Project Number Date
test_Tails_ISO_stable 5521 18 Mar 2025, 17:56

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 21:39.420 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:22.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.887
When I start Tails from USB drive "old" with network unplugged 1:44.666
Then the boot device has safe access rights 3.582
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 10.249
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:31.472
Then Tails is running from USB drive "old" 0.421
And I create a persistent partition 32.433
And I take note of which tps features are available 2.073
Then a Tails persistence partition exists on USB drive "old" 0.968
And I shutdown Tails and wait for the computer to power off 9.370
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.012
Tags: @product
3:8.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.748
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.427
Then Tails is running from USB drive "old" 0.730
And all tps features are active 2.613
When I write some files expected to persist 4.302
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 4.039
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 6.994
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.257
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.247
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.582
And I log in to a new session 20.440
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.835
Then the running Tails is installed on USB drive "to_upgrade" 20.797
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 6.974
After features/support/hooks.rb:100 0.000
Tags: @product
2:55.145
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:44.431
Then all tps features from the old Tails version are active 2.004
And Tails is running from USB drive "to_upgrade" 0.446
And the boot device has safe access rights 3.485
And the expected persistent files created with the old Tails version are present in the filesystem 1.840
And all persistent directories from the old Tails version have safe access rights 2.726
After features/support/hooks.rb:330 1.306
After features/support/hooks.rb:100 0.009
7:22.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.990
And no SquashFS delta is installed 0.142
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.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.444
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.577
When the network is plugged 0.134
And Tor is ready 22.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.361
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.580
Given I shutdown Tails and wait for the computer to power off 11.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.978
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.328
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.299
When the network is plugged 0.061
And Tor is ready 18.150
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.317
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.942
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.931
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.274
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.074
And Tor is ready 18.533
Then the Upgrader considers the system as up-to-date 10.895
# 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.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.007
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.016
40.143
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 9.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 23.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.659
After features/support/hooks.rb:330 0.771
After features/support/hooks.rb:100 0.000