Project Number Date
test_Tails_ISO_stable 6403 25 May 2026, 13:16

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:12.562 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:1.359
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.571
When I start Tails from USB drive "old" with network unplugged 43.387
Then the boot device has safe access rights 2.650
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 1.319
After features/support/hooks.rb:104 0.007
Tags: @product
1:22.126
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 52.656
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 24.104
And I take note of which tps features are available 0.350
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 4.231
After features/support/hooks.rb:335 0.210
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.982
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.330
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.340
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.898
And I take note of which tps features are available 0.210
And I shutdown Tails and wait for the computer to power off 7.864
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.216
After features/support/hooks.rb:335 0.379
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.823
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.139
And I log in to a new session 13.132
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.865
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.387
Then the running Tails is installed on USB drive "to_upgrade" 14.725
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:335 2.170
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.135
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.780
Then all tps features from the old Tails version are active 1.100
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 2.713
And the expected persistent files created with the old Tails version are present in the filesystem 1.137
And all persistent directories from the old Tails version have safe access rights 2.061
After features/support/hooks.rb:335 0.682
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:40.738
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.320
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.021
And Tor is ready 14.050
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.643
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.917
Given I shutdown Tails and wait for the computer to power off 9.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.080
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.025
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.194
When the network is plugged 0.015
And Tor is ready 11.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.356
Given I shutdown Tails and wait for the computer to power off 8.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.889
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.015
And Tor is ready 10.089
Then the Upgrader considers the system as up-to-date 10.540
# 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.164
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:335 0.695
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.396
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 10.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.323
After features/support/hooks.rb:335 0.818
After features/support/hooks.rb:104 0.000