Project Number Date
test_Tails_ISO_stable 5606 28 Apr 2025, 20:53

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 20:28.663 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:25.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.663
When I start Tails from USB drive "old" with network unplugged 1:46.212
Then the boot device has safe access rights 4.317
And Tails is running from USB drive "old" 0.503
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.397
And I unplug USB drive "old" 0.304
After features/support/hooks.rb:330 3.990
After features/support/hooks.rb:100 0.013
Tags: @product
2:19.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:34.609
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.780
And I take note of which tps features are available 2.513
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.505
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.270
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.995
Then Tails is running from USB drive "old" 0.932
And all tps features are active 2.046
When I write some files expected to persist 1.797
# 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.464
And all persistent directories from the old Tails version have safe access rights 2.649
And I take note of which tps features are available 0.627
And I shutdown Tails and wait for the computer to power off 6.530
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.799
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.014
Tags: @product
2:38.532
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.669
And I log in to a new session 20.492
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.961
And I plug USB drive "to_upgrade" 2.610
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.626
Then the running Tails is installed on USB drive "to_upgrade" 26.742
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 1.150
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.964
Then all tps features from the old Tails version are active 1.666
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.593
And the expected persistent files created with the old Tails version are present in the filesystem 1.462
And all persistent directories from the old Tails version have safe access rights 2.348
After features/support/hooks.rb:330 2.085
After features/support/hooks.rb:100 0.009
6:52.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.632
And no SquashFS delta is installed 0.551
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.557
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.092
And Tor is ready 21.016
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.942
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.915
Given I shutdown Tails and wait for the computer to power off 11.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.070
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.380
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.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.313
When the network is plugged 0.068
And Tor is ready 17.518
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.903
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.711
Given I shutdown Tails and wait for the computer to power off 6.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.004
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.089
And Tor is ready 20.534
Then the Upgrader considers the system as up-to-date 0.349
# 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 15.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.533
After features/support/hooks.rb:330 0.683
After features/support/hooks.rb:100 0.071
40.965
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.986
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 21.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.131
After features/support/hooks.rb:330 0.869
After features/support/hooks.rb:100 0.000