Project Number Date
test_Tails_ISO_stable 4692 01 Mar 2024, 16:36

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 18:17.169 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:34.738
Before features/support/hooks.rb:245 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.128
When I start Tails from USB drive "old" with network unplugged 1:10.410
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:291 6.940
After features/support/hooks.rb:75 0.008
Tags: @product
2:7.161
Before features/support/hooks.rb:245 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:12.680
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 41.967
And I take note of which tps features are available 2.071
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 9.074
After features/support/hooks.rb:291 0.194
After features/support/hooks.rb:75 0.009
Tags: @product
2:40.797
Before features/support/hooks.rb:245 0.005
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.601
Then Tails is running from USB drive "old" 0.370
And all tps features are active 1.913
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.614
And I shutdown Tails and wait for the computer to power off 4.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.300
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.010
Tags: @product
2:25.447
Before features/support/hooks.rb:245 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 10.504
And I log in to a new session 14.520
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.482
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.033
Then the running Tails is installed on USB drive "to_upgrade" 12.141
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:291 6.773
After features/support/hooks.rb:75 0.000
Tags: @product
2:14.037
Before features/support/hooks.rb:245 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.463
Then all tps features from the old Tails version are active 1.350
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.933
And the expected persistent files created with the old Tails version are present in the filesystem 1.393
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:291 0.877
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:41.485
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 11.004
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
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.415
When the network is plugged 0.037
And Tor is ready 17.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.270
Given I shutdown Tails and wait for the computer to power off 6.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.318
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.057
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.280
When the network is plugged 0.060
And Tor is ready 17.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.987
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.060
Given I shutdown Tails and wait for the computer to power off 5.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.037
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.828
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.041
And Tor is ready 17.572
Then the Upgrader considers the system as up-to-date 10.753
# 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.743
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.848
After features/support/hooks.rb:291 0.973
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
33.501
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.555
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 15.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.810
After features/support/hooks.rb:291 0.628
After features/support/hooks.rb:75 0.000