Project Number Date
test_Tails_ISO_devel 3497 30 Aug 2024, 12:39

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:1.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:15.216
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.044
When I start Tails from USB drive "old" with network unplugged 1:38.533
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.521
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.946
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:31.580
Then Tails is running from USB drive "old" 0.421
And I create a persistent partition 32.399
And I take note of which tps features are available 1.798
Then a Tails persistence partition exists on USB drive "old" 0.904
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.259
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.359
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.374
When I write some files expected to persist 1.850
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.956
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.464
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.456
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.864
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.592
And I log in to a new session 21.375
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.668
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.297
Then the running Tails is installed on USB drive "to_upgrade" 21.071
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 1.930
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.337
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.518
Then all tps features from the old Tails version are active 1.852
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.318
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.683
After features/support/hooks.rb:326 1.085
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:41.863
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.337
And no SquashFS delta is installed 0.867
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.094
And Tor is ready 19.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.239
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.940
Given I shutdown Tails and wait for the computer to power off 10.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.709
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.437
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.310
When the network is plugged 0.081
And Tor is ready 18.636
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.945
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.021
Given I shutdown Tails and wait for the computer to power off 4.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.458
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.069
And Tor is ready 19.648
Then the Upgrader considers the system as up-to-date 0.356
# 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.230
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.151
After features/support/hooks.rb:326 0.844
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.362
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.788
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.616
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.928
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 19.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.569
After features/support/hooks.rb:326 1.006
After features/support/hooks.rb:100 0.000