Project Number Date
test_Tails_ISO_stable 5305 30 Nov 2024, 08:38

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:40.968 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:27.530
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 28.192
When I start Tails from USB drive "old" with network unplugged 1:53.675
Then the boot device has safe access rights 3.222
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.145
And udev-watchdog is monitoring the correct device 0.373
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.750
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.858
Before features/support/hooks.rb:269 0.007
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:29.929
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 32.257
And I take note of which tps features are available 1.642
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.521
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.513
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.371
Then Tails is running from USB drive "old" 0.399
And all tps features are active 2.624
When I write some files expected to persist 2.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.383
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 3.740
And I take note of which tps features are available 0.622
And I shutdown Tails and wait for the computer to power off 4.430
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.072
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.339
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.567
And I log in to a new session 22.756
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.888
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.063
Then the running Tails is installed on USB drive "to_upgrade" 23.791
And I unplug USB drive "to_upgrade" 0.352
And I unplug USB drive "__internal" 0.375
After features/support/hooks.rb:326 2.925
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.876
Before features/support/hooks.rb:269 0.006
Given a computer 0.427
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.197
Then all tps features from the old Tails version are active 1.759
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.205
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.522
After features/support/hooks.rb:326 0.945
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:14.822
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.667
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.077
And Tor is ready 24.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.776
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.709
Given I shutdown Tails and wait for the computer to power off 8.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.192
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.099
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.292
When the network is plugged 0.081
And Tor is ready 19.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.327
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.411
Given I shutdown Tails and wait for the computer to power off 4.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.808
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.182
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.072
And Tor is ready 18.547
Then the Upgrader considers the system as up-to-date 0.307
# 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.134
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.873
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
39.027
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.771
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.653
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.791
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.000