Project Number Date
test_Tails_ISO_stable 5257 09 Nov 2024, 08: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 19:43.170 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:9.664
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 33.489
When I start Tails from USB drive "old" with network unplugged 1:30.399
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.794
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.053
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:22.993
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 32.604
And I take note of which tps features are available 1.317
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.686
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.959
Before features/support/hooks.rb:269 0.006
Given a computer 0.327
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.695
Then Tails is running from USB drive "old" 0.504
And all tps features are active 2.162
When I write some files expected to persist 2.068
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.413
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.036
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.617
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.549
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 14.025
And I log in to a new session 23.307
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.981
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.967
Then the running Tails is installed on USB drive "to_upgrade" 24.392
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 3.592
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.920
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.160
Then all tps features from the old Tails version are active 1.636
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.544
After features/support/hooks.rb:326 1.062
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:47.890
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 13.850
And no SquashFS delta is installed 1.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.065
And Tor is ready 24.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.999
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.083
Given I shutdown Tails and wait for the computer to power off 11.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.676
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
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.336
# 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.375
When the network is plugged 0.097
And Tor is ready 17.828
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.610
Given I shutdown Tails and wait for the computer to power off 4.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.765
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.200
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.083
And Tor is ready 17.705
Then the Upgrader considers the system as up-to-date 10.884
# 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.801
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.221
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
42.132
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.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.832
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.792
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 23.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.131
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.000