Project Number Date
test_Tails_ISO_stable 5080 08 Sep 2024, 12:13

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:34.392 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:6.331
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.228
When I start Tails from USB drive "old" with network unplugged 1:28.692
Then the boot device has safe access rights 3.106
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 7.637
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.013
Before features/support/hooks.rb:269 0.007
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login 1:21.472
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 33.496
And I take note of which tps features are available 1.366
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.308
After features/support/hooks.rb:326 0.223
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.573
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.959
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.110
When I write some files expected to persist 1.708
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.563
And all persistent directories from the old Tails version have safe access rights 2.965
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.713
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.877
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 11.621
And I log in to a new session 19.464
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.959
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.836
Then the running Tails is installed on USB drive "to_upgrade" 18.072
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 3.190
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.029
Before features/support/hooks.rb:269 0.007
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.779
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.174
And the expected persistent files created with the old Tails version are present in the filesystem 1.604
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:7.712
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.828
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.069
And Tor is ready 18.114
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.816
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.324
Given I shutdown Tails and wait for the computer to power off 10.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.172
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.899
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.278
When the network is plugged 0.068
And Tor is ready 17.106
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.113
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.277
Given I shutdown Tails and wait for the computer to power off 4.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.315
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.049
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.068
And Tor is ready 15.067
Then the Upgrader considers the system as up-to-date 10.861
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.882
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.854
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 10.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.701
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.587
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000