Project Number Date
test_Tails_ISO_stable 6470 24 Jun 2026, 11:38

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:55.411 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:0.686
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.602
When I start Tails from USB drive "old" with network unplugged 42.333
Then the boot device has safe access rights 2.713
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:339 1.439
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 54.824
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 25.517
And I take note of which tps features are available 4.603
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 7.918
After features/support/hooks.rb:339 0.190
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.932
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.974
Then Tails is running from USB drive "old" 0.266
And all tps features are active 5.163
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 1.832
And I take note of which tps features are available 3.782
And I shutdown Tails and wait for the computer to power off 8.030
# 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" 12.049
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.288
And I log in to a new session 13.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.983
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.259
Then the running Tails is installed on USB drive "to_upgrade" 14.578
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 3.637
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.316
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.753
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 3.061
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.021
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:56.986
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.210
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.016
And Tor is ready 12.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.658
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.057
Given I shutdown Tails and wait for the computer to power off 9.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.329
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.567
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.180
When the network is plugged 0.016
And Tor is ready 10.343
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.060
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.905
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.398
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.420
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.026
And Tor is ready 11.318
Then the Upgrader considers the system as up-to-date 10.552
# 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 5.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:339 0.968
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.660
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.746
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.000