Project Number Date
test_Tails_ISO_stable 6430 05 Jun 2026, 11:29

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 10:56.540 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
57.688
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
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.214
When I start Tails from USB drive "old" with network unplugged 40.201
Then the boot device has safe access rights 2.536
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:335 3.418
After features/support/hooks.rb:104 0.005
Tags: @product
1:25.819
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 52.582
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 23.940
And I take note of which tps features are available 0.321
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.090
After features/support/hooks.rb:335 0.565
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.843
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.905
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.143
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 1.854
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 7.776
# 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" 11.827
After features/support/hooks.rb:335 0.448
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.845
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.658
And I log in to a new session 11.471
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.975
Then the running Tails is installed on USB drive "to_upgrade" 14.457
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.035
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.843
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.841
Then all tps features from the old Tails version are active 1.175
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.129
And all persistent directories from the old Tails version have safe access rights 1.864
After features/support/hooks.rb:335 0.827
After features/support/hooks.rb:104 0.006
3:32.592
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.091
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.014
And Tor is ready 12.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.323
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.065
Given I shutdown Tails and wait for the computer to power off 9.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.924
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# 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.206
When the network is plugged 0.018
And Tor is ready 10.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.904
Given I shutdown Tails and wait for the computer to power off 3.976
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.075
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.016
And Tor is ready 11.503
Then the Upgrader considers the system as up-to-date 10.570
# 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.179
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:335 0.890
After features/support/hooks.rb:104 0.010
19.909
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.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.071
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 9.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.636
After features/support/hooks.rb:335 0.820
After features/support/hooks.rb:104 0.000