Project Number Date
test_Tails_ISO_stable 4827 05 May 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:23.973 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:57.890
Before features/support/hooks.rb:259 0.006
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.843
When I start Tails from USB drive "old" with network unplugged 1:21.852
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 7.060
After features/support/hooks.rb:89 0.010
Tags: @product
2:12.501
Before features/support/hooks.rb:259 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:26.336
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 35.260
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.751
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:305 0.156
After features/support/hooks.rb:89 0.012
Tags: @product
2:41.481
Before features/support/hooks.rb:259 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.088
Then Tails is running from USB drive "old" 0.448
And all tps features are active 1.853
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.417
And I take note of which tps features are available 0.381
And I shutdown Tails and wait for the computer to power off 4.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.700
After features/support/hooks.rb:305 0.115
After features/support/hooks.rb:89 0.011
Tags: @product
2:25.613
Before features/support/hooks.rb:259 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.241
And I log in to a new session 18.574
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.840
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.033
Then the running Tails is installed on USB drive "to_upgrade" 16.188
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:305 2.501
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.765
Before features/support/hooks.rb:259 0.010
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.503
Then all tps features from the old Tails version are active 1.671
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.048
And the expected persistent files created with the old Tails version are present in the filesystem 1.630
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:305 0.816
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:13.047
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.503
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.050
And Tor is ready 22.967
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.680
Given I shutdown Tails and wait for the computer to power off 8.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.533
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.271
When the network is plugged 0.038
And Tor is ready 18.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.114
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.776
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.267
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.922
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.041
And Tor is ready 20.094
Then the Upgrader considers the system as up-to-date 0.296
# 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.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.911
After features/support/hooks.rb:305 0.793
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
35.673
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.620
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.832
After features/support/hooks.rb:305 0.715
After features/support/hooks.rb:89 0.000