Project Number Date
test_Tails_ISO_stable 6017 20 Dec 2025, 11:35

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 13:14.066 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
1:28.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 29.055
When I start Tails from USB drive "old" with network unplugged 53.557
Then the boot device has safe access rights 3.291
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 3.836
After features/support/hooks.rb:100 0.010
Tags: @product
1:41.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:2.528
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 29.264
And I take note of which tps features are available 1.133
Then a Tails persistence partition exists on USB drive "old" 0.734
And I shutdown Tails and wait for the computer to power off 7.637
After features/support/hooks.rb:331 0.611
After features/support/hooks.rb:100 0.010
Tags: @product
1:52.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.239
Then Tails is running from USB drive "old" 0.592
And all tps features are active 7.023
When I write some files expected to persist 1.560
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.408
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.958
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.107
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.836
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 without a persistent partition and stopped at Tails Greeter's login screen 10.011
And I log in to a new session 11.180
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.967
And I plug USB drive "to_upgrade" 2.307
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.773
Then the running Tails is installed on USB drive "to_upgrade" 19.183
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 3.957
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.534
Then all tps features from the old Tails version are active 1.419
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.284
And the expected persistent files created with the old Tails version are present in the filesystem 1.359
And all persistent directories from the old Tails version have safe access rights 3.141
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:3.596
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 9.958
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.057
And Tor is ready 12.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.991
Given I shutdown Tails and wait for the computer to power off 7.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.391
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.481
When the network is plugged 0.134
And Tor is ready 12.485
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.994
Given I shutdown Tails and wait for the computer to power off 8.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.216
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.671
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.196
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.052
And Tor is ready 10.717
Then the Upgrader considers the system as up-to-date 0.130
# 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 6.896
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.657
After features/support/hooks.rb:331 1.140
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
20.481
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 9.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 10.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.619
After features/support/hooks.rb:331 0.934
After features/support/hooks.rb:100 0.000