Project Number Date
test_Tails_ISO_stable 4763 02 Apr 2024, 23:14

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:59.219 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:48.347
Before features/support/hooks.rb:245 0.008
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 22.351
When I start Tails from USB drive "old" with network unplugged 1:20.711
Then the boot device has safe access rights 2.982
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:291 4.070
After features/support/hooks.rb:75 0.014
Tags: @product
2:2.848
Before features/support/hooks.rb:245 0.013
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:17.980
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 33.441
And I take note of which tps features are available 1.705
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 8.346
After features/support/hooks.rb:291 0.221
After features/support/hooks.rb:75 0.009
Tags: @product
2:39.849
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.955
Then Tails is running from USB drive "old" 0.325
And all tps features are active 1.844
When I write some files expected to persist 1.600
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.492
And I take note of which tps features are available 0.573
And I shutdown Tails and wait for the computer to power off 4.235
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.123
After features/support/hooks.rb:291 0.142
After features/support/hooks.rb:75 0.007
Tags: @product
2:19.230
Before features/support/hooks.rb:245 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.798
And I log in to a new session 14.953
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.390
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.448
Then the running Tails is installed on USB drive "to_upgrade" 13.838
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 3.564
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.791
Before features/support/hooks.rb:245 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 1:51.152
Then all tps features from the old Tails version are active 2.198
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 2.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.671
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:291 0.873
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
8:12.831
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.906
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.039
And Tor is ready 19.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.850
Given I shutdown Tails and wait for the computer to power off 8.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.730
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.074
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.038
And Tor is ready 18.506
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.103
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 2:14.849
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 1:50.100
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.784
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.074
And Tor is ready 19.294
Then the Upgrader considers the system as up-to-date 0.253
# 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 13.601
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.858
After features/support/hooks.rb:291 0.716
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
55.320
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.742
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 43.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.578
After features/support/hooks.rb:291 0.680
After features/support/hooks.rb:75 0.000