Project Number Date
test_Tails_ISO_stable 5091 11 Sep 2024, 08:48

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 21:15.508 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:29.105
Before features/support/hooks.rb:269 0.004
Given a computer 1.636
And I create a 7200 MiB disk named "old" 0.318
And I plug USB drive "old" 1.195
And I write an old version of the Tails USB image to disk "old" 42.310
When I start Tails from USB drive "old" with network unplugged 1:38.993
Then the boot device has safe access rights 3.568
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 9.302
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.357
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:27.216
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 32.246
And I take note of which tps features are available 2.046
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.497
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.562
Before features/support/hooks.rb:269 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.138
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.046
When I write some files expected to persist 1.775
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 4.119
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.538
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.222
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 13.246
And I log in to a new session 20.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.827
And I plug USB drive "to_upgrade" 2.711
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.931
Then the running Tails is installed on USB drive "to_upgrade" 20.273
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:326 3.598
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.030
Before features/support/hooks.rb:269 0.008
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.602
Then all tps features from the old Tails version are active 1.688
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.806
And the expected persistent files created with the old Tails version are present in the filesystem 1.657
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:326 0.935
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
8:2.958
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 12.857
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.428
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.079
And Tor is ready 20.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.278
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.192
Given I shutdown Tails and wait for the computer to power off 1:31.843
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.465
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.833
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.289
When the network is plugged 0.090
And Tor is ready 18.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.014
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.408
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.206
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.174
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.090
And Tor is ready 21.088
Then the Upgrader considers the system as up-to-date 0.371
# 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.048
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.270
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 11.238
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.926
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 19.023
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.591
After features/support/hooks.rb:326 1.078
After features/support/hooks.rb:100 0.000