Project Number Date
test_Tails_ISO_stable 6222 23 Mar 2026, 11:23

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:42.965 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:36.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.174
When I start Tails from USB drive "old" with network unplugged 1:17.464
Then the boot device has safe access rights 2.819
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.823
After features/support/hooks.rb:100 0.018
Tags: @product
1:25.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 55.952
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 23.893
And I take note of which tps features are available 0.877
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 3.989
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.251
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.144
When I write some files expected to persist 1.641
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 2.118
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.408
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.429
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.972
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 without a persistent partition and stopped at Tails Greeter's login screen 8.948
And I log in to a new session 22.973
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.917
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.038
Then the running Tails is installed on USB drive "to_upgrade" 17.508
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 5.311
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.977
Then all tps features from the old Tails version are active 1.145
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 2.832
And the expected persistent files created with the old Tails version are present in the filesystem 1.285
And all persistent directories from the old Tails version have safe access rights 2.217
After features/support/hooks.rb:331 0.928
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
4:52.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.960
And no SquashFS delta is installed 0.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.440
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.013
And Tor is ready 29.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.444
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.570
Given I shutdown Tails and wait for the computer to power off 21.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.786
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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 21.210
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.445
Given I shutdown Tails and wait for the computer to power off 18.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.281
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.019
And Tor is ready 20.231
Then the Upgrader considers the system as up-to-date 0.119
# 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.233
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:331 0.757
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
28.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.938
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
After features/support/hooks.rb:331 0.772
After features/support/hooks.rb:100 0.000