Project Number Date
test_Tails_ISO_devel 3622 25 Dec 2024, 12:22

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:54.244 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:10.626
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.343
When I start Tails from USB drive "old" with network unplugged 1:33.765
Then the boot device has safe access rights 3.322
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.496
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.129
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:25.506
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 29.144
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.294
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.806
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.965
Then Tails is running from USB drive "old" 0.476
And all tps features are active 1.992
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.884
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.064
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.360
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.271
And I log in to a new session 19.223
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.507
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.150
Then the running Tails is installed on USB drive "to_upgrade" 19.432
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 6.989
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.504
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.333
Then all tps features from the old Tails version are active 1.579
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.008
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:326 0.579
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.834
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 14.089
And no SquashFS delta is installed 0.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
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.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.066
And Tor is ready 18.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.236
Given I shutdown Tails and wait for the computer to power off 10.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.883
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.012
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
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.309
# 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.295
When the network is plugged 0.067
And Tor is ready 17.127
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.325
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.843
Given I shutdown Tails and wait for the computer to power off 4.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.853
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
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.301
When the network is plugged 0.072
And Tor is ready 17.767
Then the Upgrader considers the system as up-to-date 0.294
# 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.932
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.041
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.982
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.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.622
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 1.016
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 20.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.074
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.000