Project Number Date
test_Tails_ISO_stable 5969 26 Nov 2025, 09: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 17:51.246 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
2:29.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 55.418
When I start Tails from USB drive "old" with network unplugged 1:28.424
Then the boot device has safe access rights 3.472
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:331 3.722
After features/support/hooks.rb:100 0.050
Tags: @product
2:16.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:28.946
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 31.357
And I take note of which tps features are available 5.706
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 8.910
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.515
Then Tails is running from USB drive "old" 0.827
And all tps features are active 2.389
When I write some files expected to persist 1.665
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.440
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 7.762
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.252
After features/support/hooks.rb:331 0.374
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.713
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 13.718
And I log in to a new session 18.850
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.416
And I plug USB drive "to_upgrade" 3.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.141
Then the running Tails is installed on USB drive "to_upgrade" 22.930
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.933
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.175
Then all tps features from the old Tails version are active 1.999
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 4.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.348
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
5:40.774
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.878
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.151
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.867
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.140
And Tor is ready 15.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.869
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.748
Given I shutdown Tails and wait for the computer to power off 11.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.113
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.774
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.204
# 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.373
When the network is plugged 0.109
And Tor is ready 42.230
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.520
Given I shutdown Tails and wait for the computer to power off 8.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.116
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.961
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.071
And Tor is ready 11.172
Then the Upgrader considers the system as up-to-date 0.211
# 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 7.046
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.757
After features/support/hooks.rb:331 1.087
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 11.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.718
After features/support/hooks.rb:331 0.787
After features/support/hooks.rb:100 0.000