Project Number Date
test_Tails_ISO_devel 4045 31 Oct 2025, 10:04

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 16:20.757 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:45.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.097
And I write an old version of the Tails USB image to disk "old" 27.071
When I start Tails from USB drive "old" with network unplugged 1:11.764
Then the boot device has safe access rights 3.991
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 4.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:28.762
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 30.312
And I take note of which tps features are available 3.223
Then a Tails persistence partition exists on USB drive "old" 0.712
And I shutdown Tails and wait for the computer to power off 10.033
After features/support/hooks.rb:331 0.467
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.293
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.969
Then Tails is running from USB drive "old" 0.829
And all tps features are active 2.240
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.289
And I take note of which tps features are available 0.573
And I shutdown Tails and wait for the computer to power off 7.700
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.153
After features/support/hooks.rb:331 0.537
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.277
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 10.742
And I log in to a new session 17.028
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.150
And I plug USB drive "to_upgrade" 2.328
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.131
Then the running Tails is installed on USB drive "to_upgrade" 21.452
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:331 3.834
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.940
Then all tps features from the old Tails version are active 1.954
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.767
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.690
After features/support/hooks.rb:331 1.007
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:13.367
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 with a persistent partition enabled and logged in 10.328
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.066
And Tor is ready 13.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.960
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.329
Given I shutdown Tails and wait for the computer to power off 11.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.645
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 3.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.206
# 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.286
When the network is plugged 0.075
And Tor is ready 11.218
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.412
Given I shutdown Tails and wait for the computer to power off 7.752
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.586
Then Tails is running version 6.3~testoverlayfs 0.050
And all tps features are active 2.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.111
# 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.228
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.343
When the network is plugged 0.067
And Tor is ready 12.635
Then the Upgrader considers the system as up-to-date 0.264
# 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 6.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.456
After features/support/hooks.rb:331 1.026
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.526
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 10.774
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 13.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.593
After features/support/hooks.rb:331 1.073
After features/support/hooks.rb:100 0.000