Project Number Date
test_Tails_ISO_devel 3716 03 Mar 2025, 18:57

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:28.296 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:2.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.404
When I start Tails from USB drive "old" with network unplugged 1:24.829
Then the boot device has safe access rights 3.097
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 8.683
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.346
And I start Tails from USB drive "old" with network unplugged and I login 1:25.924
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.844
And I take note of which tps features are available 1.244
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.372
After features/support/hooks.rb:330 0.292
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.924
Then Tails is running from USB drive "old" 0.701
And all tps features are active 1.909
When I write some files expected to persist 1.846
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 4.093
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 6.670
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.808
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.012
Tags: @product
2:39.085
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 without a persistent partition and stopped at Tails Greeter's login screen 9.760
And I log in to a new session 18.514
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.715
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.879
Then the running Tails is installed on USB drive "to_upgrade" 21.247
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:330 2.170
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.728
Then all tps features from the old Tails version are active 2.241
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.723
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.444
After features/support/hooks.rb:330 1.403
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:38.616
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 11.540
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.431
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.090
And Tor is ready 20.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.158
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.050
Given I shutdown Tails and wait for the computer to power off 8.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.392
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.303
When the network is plugged 0.067
And Tor is ready 20.506
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.085
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.889
Given I shutdown Tails and wait for the computer to power off 4.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.411
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.985
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.071
And Tor is ready 16.879
Then the Upgrader considers the system as up-to-date 10.920
# 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 15.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.938
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.521
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 9.804
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.101
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.782
After features/support/hooks.rb:330 0.764
After features/support/hooks.rb:100 0.000