Project Number Date
test_Tails_ISO_stable 5358 27 Dec 2024, 12:23

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:2.911 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:3.032
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.416
When I start Tails from USB drive "old" with network unplugged 1:27.200
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.505
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.134
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:24.049
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 29.782
And I take note of which tps features are available 1.736
Then a Tails persistence partition exists on USB drive "old" 0.738
And I shutdown Tails and wait for the computer to power off 8.301
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.835
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.358
Then Tails is running from USB drive "old" 0.856
And all tps features are active 1.893
When I write some files expected to persist 1.823
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.220
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.154
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.551
Before features/support/hooks.rb:269 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 11.728
And I log in to a new session 18.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.724
And I plug USB drive "to_upgrade" 2.673
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.906
Then the running Tails is installed on USB drive "to_upgrade" 21.076
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 1.891
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.039
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.940
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.469
And all persistent directories from the old Tails version have safe access rights 2.236
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.013
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.836
And no SquashFS delta is installed 0.463
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.061
And Tor is ready 21.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.812
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.155
Given I shutdown Tails and wait for the computer to power off 12.971
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.221
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.478
When the network is plugged 0.095
And Tor is ready 15.707
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.640
Given I shutdown Tails and wait for the computer to power off 4.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.861
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.077
And Tor is ready 17.898
Then the Upgrader considers the system as up-to-date 0.318
# 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.452
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.146
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.304
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.638
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 23.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.114
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000