Project Number Date
test_Tails_ISO_stable 6710 30 Sep 2026, 14:11

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:53.524 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:17.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 18.424
When I start Tails from USB drive "old" with network unplugged 55.403
Then the boot device has safe access rights 2.338
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:339 3.575
After features/support/hooks.rb:108 0.073
Tags: @product
1:26.770
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 50.612
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 25.909
And I take note of which tps features are available 6.697
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 2.627
After features/support/hooks.rb:339 0.609
After features/support/hooks.rb:108 0.006
Tags: @product
1:44.202
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.399
Then Tails is running from USB drive "old" 0.262
And all tps features are active 9.130
When I write some files expected to persist 1.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.870
And I take note of which tps features are available 7.914
And I shutdown Tails and wait for the computer to power off 4.000
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.841
After features/support/hooks.rb:339 0.125
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.365
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.224
And I log in to a new session 11.285
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.993
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.068
Then the running Tails is installed on USB drive "to_upgrade" 18.289
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 1.837
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.676
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.055
Then all tps features from the old Tails version are active 1.457
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 2.757
And the expected persistent files created with the old Tails version are present in the filesystem 1.120
And all persistent directories from the old Tails version have safe access rights 1.852
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:38.492
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.540
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.036
And Tor is ready 12.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.559
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.605
Given I shutdown Tails and wait for the computer to power off 5.718
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.482
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.967
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.027
And Tor is ready 10.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.400
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.857
Given I shutdown Tails and wait for the computer to power off 2.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.201
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 9.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.026
And Tor is ready 10.771
Then the Upgrader considers the system as up-to-date 0.136
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 4.357
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
20.065
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.738
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 10.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.000