Project Number Date
test_Tails_ISO_test-suite-options 6 22 Jun 2025, 21: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 27:28.477 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
3:15.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 43.791
When I start Tails from USB drive "old" with network unplugged 2:19.157
Then the boot device has safe access rights 5.470
And Tails is running from USB drive "old" 2.112
And there is no persistence partition on USB drive "old" 0.167
And process "udev-watchdog" is running 0.223
And udev-watchdog is monitoring the correct device 0.510
And I unplug USB drive "old" 2.225
After features/support/hooks.rb:330 4.734
After features/support/hooks.rb:100 0.010
Tags: @product
3:14.968
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 2:6.495
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 49.275
And I take note of which tps features are available 3.355
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 14.410
After features/support/hooks.rb:330 0.249
After features/support/hooks.rb:100 0.014
Tags: @product
4:5.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.915
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:7.177
Then Tails is running from USB drive "old" 0.988
And all tps features are active 2.857
When I write some files expected to persist 6.507
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.600
And all persistence configuration files have safe access rights 0.974
And all persistent directories from the old Tails version have safe access rights 4.694
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.728
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.759
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.029
Tags: @product
3:15.841
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 14.476
And I log in to a new session 24.966
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.510
And I plug USB drive "to_upgrade" 2.539
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.616
Then the running Tails is installed on USB drive "to_upgrade" 41.878
And I unplug USB drive "to_upgrade" 0.286
And I unplug USB drive "__internal" 0.567
After features/support/hooks.rb:330 3.055
After features/support/hooks.rb:100 0.000
Tags: @product
3:2.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:46.823
Then all tps features from the old Tails version are active 5.029
And Tails is running from USB drive "to_upgrade" 1.284
And the boot device has safe access rights 5.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.802
After features/support/hooks.rb:330 2.613
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:35.829
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 with a persistent partition enabled and logged in 18.492
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.153
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.680
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.152
And Tor is ready 32.835
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.423
Given I shutdown Tails and wait for the computer to power off 13.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.563
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.979
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.287
When the network is plugged 0.074
And Tor is ready 28.131
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.020
Given I shutdown Tails and wait for the computer to power off 6.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:11.727
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.569
And the file system changes introduced in version 6.3~testoverlayfs are present 0.605
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.072
And Tor is ready 25.413
Then the Upgrader considers the system as up-to-date 11.390
# 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 22.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.407
After features/support/hooks.rb:330 0.776
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
58.195
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 13.400
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.215
But a current signing key is available on our website 0.000
When the network is plugged 0.184
And Tor is ready 29.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.786
After features/support/hooks.rb:330 2.739
After features/support/hooks.rb:100 0.000