Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 5 16 Apr 2025, 21:56

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 20:10.830 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:58.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.074
When I start Tails from USB drive "old" with network unplugged 1:21.867
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 6.925
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:21.068
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 30.300
And I take note of which tps features are available 1.799
Then a Tails persistence partition exists on USB drive "old" 0.748
And I shutdown Tails and wait for the computer to power off 8.099
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.835
Then Tails is running from USB drive "old" 0.579
And all tps features are active 1.826
When I write some files expected to persist 1.697
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.319
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.740
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.867
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.721
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 9.824
And I log in to a new session 18.341
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.641
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.052
Then the running Tails is installed on USB drive "to_upgrade" 25.986
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 2.086
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.638
Then all tps features from the old Tails version are active 1.446
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 2.999
And the expected persistent files created with the old Tails version are present in the filesystem 1.271
And all persistent directories from the old Tails version have safe access rights 2.143
After features/support/hooks.rb:330 1.227
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:0.223
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.171
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.082
And Tor is ready 23.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.009
Given I shutdown Tails and wait for the computer to power off 1:13.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.514
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.257
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
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.371
# 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.267
When the network is plugged 0.061
And Tor is ready 20.670
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.488
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.725
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.917
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.075
And Tor is ready 47.511
Then the Upgrader considers the system as up-to-date 0.318
# 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 14.762
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.503
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.990
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.946
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.938
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.527
After features/support/hooks.rb:330 1.004
After features/support/hooks.rb:100 0.000