Project Number Date
test_Tails_ISO_stable 6581 15 Aug 2026, 11:49

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 12:25.648 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:16.640
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.286
When I start Tails from USB drive "old" with network unplugged 59.277
Then the boot device has safe access rights 2.256
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.434
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.375
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login 49.266
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 23.408
And I take note of which tps features are available 6.613
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 4.089
After features/support/hooks.rb:339 0.468
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.090
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.838
Then Tails is running from USB drive "old" 0.417
And all tps features are active 7.458
When I write some files expected to persist 1.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.274
And I take note of which tps features are available 6.580
And I shutdown Tails and wait for the computer to power off 2.606
# 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.975
After features/support/hooks.rb:339 0.255
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.600
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 8.416
And I log in to a new session 12.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.272
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.471
Then the running Tails is installed on USB drive "to_upgrade" 19.450
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 3.682
After features/support/hooks.rb:108 0.000
Tags: @product
1:23.397
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.187
Then all tps features from the old Tails version are active 3.806
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.506
And the expected persistent files created with the old Tails version are present in the filesystem 1.197
And all persistent directories from the old Tails version have safe access rights 2.393
After features/support/hooks.rb:339 0.864
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
4:9.293
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 with a persistent partition enabled and logged in 25.334
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.042
And Tor is ready 14.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.751
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.782
Given I shutdown Tails and wait for the computer to power off 5.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.165
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.185
When the network is plugged 0.033
And Tor is ready 11.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.054
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.757
Given I shutdown Tails and wait for the computer to power off 4.130
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.007
And all tps features are active 8.813
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.031
And Tor is ready 10.330
Then the Upgrader considers the system as up-to-date 10.487
# 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 3.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.336
After features/support/hooks.rb:339 0.663
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
20.250
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 8.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.601
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.000