Project Number Date
test_Tails_ISO_stable 6609 26 Aug 2026, 18:02

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:37.299 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:11.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.598
When I start Tails from USB drive "old" with network unplugged 54.262
Then the boot device has safe access rights 2.227
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:339 3.757
After features/support/hooks.rb:108 0.004
Tags: @product
1:21.221
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 47.767
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 23.419
And I take note of which tps features are available 6.582
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 2.648
After features/support/hooks.rb:339 0.157
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.304
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.435
Then Tails is running from USB drive "old" 0.252
And all tps features are active 6.836
When I write some files expected to persist 1.169
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 1.503
And I take note of which tps features are available 6.732
And I shutdown Tails and wait for the computer to power off 2.589
# 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.249
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.308
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.665
And I log in to a new session 10.375
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.194
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.399
Then the running Tails is installed on USB drive "to_upgrade" 18.833
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 3.958
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.363
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.373
Then all tps features from the old Tails version are active 1.237
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.601
And the expected persistent files created with the old Tails version are present in the filesystem 1.041
And all persistent directories from the old Tails version have safe access rights 1.786
After features/support/hooks.rb:339 0.838
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:51.129
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 21.884
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.039
And Tor is ready 12.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.253
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.824
Given I shutdown Tails and wait for the computer to power off 5.363
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.653
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.928
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.207
When the network is plugged 0.028
And Tor is ready 10.237
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.629
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.401
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.278
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.085
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.032
And Tor is ready 9.556
Then the Upgrader considers the system as up-to-date 10.403
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.263
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.139
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 8.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.548
After features/support/hooks.rb:339 0.515
After features/support/hooks.rb:108 0.000