Project Number Date
test_Tails_ISO_stable 6302 15 Apr 2026, 07:41

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 13:31.160 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:18.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 14.495
When I start Tails from USB drive "old" with network unplugged 59.620
Then the boot device has safe access rights 2.856
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.270
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 58.295
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 26.484
And I take note of which tps features are available 0.722
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 4.311
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.690
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.143
When I write some files expected to persist 1.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.037
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.528
After features/support/hooks.rb:331 0.584
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.345
And I log in to a new session 18.199
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.854
Then the running Tails is installed on USB drive "to_upgrade" 17.764
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:331 3.115
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.854
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 3.040
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:331 1.102
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:59.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.268
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.018
And Tor is ready 23.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.179
Given I shutdown Tails and wait for the computer to power off 21.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.401
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.225
When the network is plugged 0.016
And Tor is ready 20.917
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.414
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.291
Given I shutdown Tails and wait for the computer to power off 18.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.202
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.013
And Tor is ready 22.309
Then the Upgrader considers the system as up-to-date 0.096
# 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.048
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.632
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.067
Tags: @product @automatic_upgrade
29.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 20.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 0.721
After features/support/hooks.rb:100 0.000