Project Number Date
test_Tails_ISO_stable 5510 12 Mar 2025, 11:55

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 19:43.851 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:13.472
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.948
When I start Tails from USB drive "old" with network unplugged 1:38.049
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.563
After features/support/hooks.rb:100 0.043
Tags: @product
2:13.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:31.014
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.166
And I take note of which tps features are available 1.875
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.843
Then Tails is running from USB drive "old" 0.955
And all tps features are active 2.019
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.314
And all persistence configuration files have safe access rights 1.144
And all persistent directories from the old Tails version have safe access rights 2.532
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 6.678
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.069
After features/support/hooks.rb:330 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.229
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 without a persistent partition and stopped at Tails Greeter's login screen 12.217
And I log in to a new session 20.677
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.653
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.472
Then the running Tails is installed on USB drive "to_upgrade" 19.049
And I unplug USB drive "to_upgrade" 0.323
And I unplug USB drive "__internal" 0.432
After features/support/hooks.rb:330 2.890
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.853
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.615
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.414
After features/support/hooks.rb:330 1.017
After features/support/hooks.rb:100 0.011
6:40.536
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 14.214
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.688
When the network is plugged 0.114
And Tor is ready 22.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.189
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.492
Given I shutdown Tails and wait for the computer to power off 8.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.199
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
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.325
# 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.272
When the network is plugged 0.139
And Tor is ready 20.532
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.320
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.262
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.605
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.087
And Tor is ready 21.084
Then the Upgrader considers the system as up-to-date 0.324
# 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 17.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.188
After features/support/hooks.rb:330 0.867
After features/support/hooks.rb:100 0.038
39.249
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 10.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.856
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 22.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.503
After features/support/hooks.rb:330 0.696
After features/support/hooks.rb:100 0.000