Project Number Date
test_Tails_ISO_stable 6247 30 Mar 2026, 11:53

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:53.445 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:5.087
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.340
When I start Tails from USB drive "old" with network unplugged 1:47.418
Then the boot device has safe access rights 2.540
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.470
After features/support/hooks.rb:100 0.033
Tags: @product
1:26.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.098
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.743
And I take note of which tps features are available 0.607
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 6.628
After features/support/hooks.rb:331 0.506
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.233
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.301
When I write some files expected to persist 1.448
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.122
And I take note of which tps features are available 0.182
And I shutdown Tails and wait for the computer to power off 8.303
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.061
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.821
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 8.538
And I log in to a new session 19.282
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.840
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.692
Then the running Tails is installed on USB drive "to_upgrade" 15.926
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:331 15.295
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.384
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.028
And all persistent directories from the old Tails version have safe access rights 1.869
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.006
4:36.413
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.060
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.021
And Tor is ready 24.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.437
Given I shutdown Tails and wait for the computer to power off 20.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.145
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.205
When the network is plugged 0.019
And Tor is ready 20.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.114
Given I shutdown Tails and wait for the computer to power off 17.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.878
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.308
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.014
And Tor is ready 20.979
Then the Upgrader considers the system as up-to-date 0.092
# 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.375
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.011
49.306
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 with a persistent partition enabled and logged in 7.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 41.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 1.115
After features/support/hooks.rb:100 0.000