Project Number Date
test_Tails_ISO_stable 5561 09 Apr 2025, 13:00

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 19:48.755 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.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.399
And I create a 7200 MiB disk named "old" 0.110
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.822
When I start Tails from USB drive "old" with network unplugged 1:32.951
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 7.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.371
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:25.734
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 31.066
And I take note of which tps features are available 1.649
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 8.588
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.104
Then Tails is running from USB drive "old" 1.429
And all tps features are active 2.141
When I write some files expected to persist 3.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 3.444
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 6.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.990
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.429
And I log in to a new session 20.924
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.109
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.856
Then the running Tails is installed on USB drive "to_upgrade" 24.540
And I unplug USB drive "to_upgrade" 0.280
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:330 0.926
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.414
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.585
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.480
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:330 1.326
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.562
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 with a persistent partition enabled and logged in 13.557
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.655
When the network is plugged 0.098
And Tor is ready 23.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.895
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.269
Given I shutdown Tails and wait for the computer to power off 8.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.399
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.874
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# 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.256
When the network is plugged 0.066
And Tor is ready 18.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.128
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.016
Given I shutdown Tails and wait for the computer to power off 4.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.154
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 1.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.467
When the network is plugged 0.073
And Tor is ready 19.617
Then the Upgrader considers the system as up-to-date 0.309
# 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 16.819
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.942
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.517
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 11.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.317
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.084
But a current signing key is available on our website 0.000
When the network is plugged 0.302
And Tor is ready 20.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.733
After features/support/hooks.rb:330 3.197
After features/support/hooks.rb:100 0.000