Project Number Date
test_Tails_ISO_stable 5037 19 Aug 2024, 20:28

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:9.489 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:12.094
Before features/support/hooks.rb:269 0.006
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.164
When I start Tails from USB drive "old" with network unplugged 1:35.604
Then the boot device has safe access rights 3.043
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.468
After features/support/hooks.rb:100 0.015
Tags: @product
2:0.924
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:19.781
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.891
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.907
And I shutdown Tails and wait for the computer to power off 6.356
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.755
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.656
Then Tails is running from USB drive "old" 0.351
And all tps features are active 1.949
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.344
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.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.168
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.018
Tags: @product
2:25.768
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 10.478
And I log in to a new session 16.652
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.045
And I plug USB drive "to_upgrade" 2.352
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.261
Then the running Tails is installed on USB drive "to_upgrade" 20.508
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 1.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.459
Before features/support/hooks.rb:269 0.008
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.326
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.074
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.428
After features/support/hooks.rb:326 0.866
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:50.650
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 12.220
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.062
And Tor is ready 18.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.044
Given I shutdown Tails and wait for the computer to power off 10.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.476
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.061
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.300
When the network is plugged 0.091
And Tor is ready 20.674
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.075
Given I shutdown Tails and wait for the computer to power off 4.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.205
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.880
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.091
And Tor is ready 47.308
Then the Upgrader considers the system as up-to-date 0.312
# 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.827
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
44.835
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 17.948
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
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.848
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.000