Project Number Date
test_Tails_ISO_stable 5455 12 Feb 2025, 21:01

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:23.899 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:21.920
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.719
When I start Tails from USB drive "old" with network unplugged 1:45.388
Then the boot device has safe access rights 3.444
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:326 7.262
After features/support/hooks.rb:100 0.053
Tags: @product
2:14.514
Before features/support/hooks.rb:269 0.016
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:28.185
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 33.161
And I take note of which tps features are available 2.686
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.987
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.742
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.738
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.343
When I write some files expected to persist 2.090
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.521
And I take note of which tps features are available 0.610
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.741
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.082
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 11.281
And I log in to a new session 19.685
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.964
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.905
Then the running Tails is installed on USB drive "to_upgrade" 23.336
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.007
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.969
Before features/support/hooks.rb:269 0.008
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.857
Then all tps features from the old Tails version are active 1.866
And Tails is running from USB drive "to_upgrade" 0.440
And the boot device has safe access rights 3.654
And the expected persistent files created with the old Tails version are present in the filesystem 1.592
And all persistent directories from the old Tails version have safe access rights 3.335
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:10.018
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.774
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
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.455
When the network is plugged 0.094
And Tor is ready 18.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.647
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.316
Given I shutdown Tails and wait for the computer to power off 8.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.629
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.406
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# 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.283
When the network is plugged 0.090
And Tor is ready 20.989
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.992
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.573
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.314
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.338
When the network is plugged 0.091
And Tor is ready 48.146
Then the Upgrader considers the system as up-to-date 0.358
# 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.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.073
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
35.651
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.537
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 17.378
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.419
After features/support/hooks.rb:326 0.796
After features/support/hooks.rb:100 0.000