Project Number Date
test_Tails_ISO_stable 6029 31 Dec 2025, 12:44

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 11:4.559 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:10.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.017
When I start Tails from USB drive "old" with network unplugged 52.870
Then the boot device has safe access rights 2.568
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.431
After features/support/hooks.rb:100 0.024
Tags: @product
1:25.131
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.114
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 23.669
And I take note of which tps features are available 0.579
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 7.928
After features/support/hooks.rb:331 0.262
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.765
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.258
Then Tails is running from USB drive "old" 0.223
And all tps features are active 1.091
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 1.798
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 7.789
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.711
After features/support/hooks.rb:331 0.536
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.626
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.981
And I log in to a new session 11.874
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.667
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.320
Then the running Tails is installed on USB drive "to_upgrade" 14.291
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:331 3.693
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.371
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.951
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.443
And the expected persistent files created with the old Tails version are present in the filesystem 1.018
And all persistent directories from the old Tails version have safe access rights 1.767
After features/support/hooks.rb:331 0.846
After features/support/hooks.rb:100 0.006
3:32.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.004
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.016
And Tor is ready 13.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.288
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.480
Given I shutdown Tails and wait for the computer to power off 10.931
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.728
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.183
When the network is plugged 0.016
And Tor is ready 9.612
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.821
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.833
Given I shutdown Tails and wait for the computer to power off 8.081
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.736
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.020
And Tor is ready 9.695
Then the Upgrader considers the system as up-to-date 10.490
# 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 4.206
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:331 1.033
After features/support/hooks.rb:100 0.010
19.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.489
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.000