Project Number Date
test_Tails_ISO_stable 6547 30 Jul 2026, 00:32

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:43.401 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
55.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.443
When I start Tails from USB drive "old" with network unplugged 38.024
Then the boot device has safe access rights 1.866
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.138
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.499
After features/support/hooks.rb:108 0.008
Tags: @product
1:17.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 45.641
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 22.276
And I take note of which tps features are available 6.319
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 2.599
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.741
Then Tails is running from USB drive "old" 0.195
And all tps features are active 6.745
When I write some files expected to persist 0.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.230
And all persistent directories from the old Tails version have safe access rights 1.352
And I take note of which tps features are available 5.806
And I shutdown Tails and wait for the computer to power off 2.494
# 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" 10.869
After features/support/hooks.rb:339 0.257
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.795
And I log in to a new session 10.194
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.699
Then the running Tails is installed on USB drive "to_upgrade" 17.569
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.658
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.722
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.279
Then all tps features from the old Tails version are active 0.965
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 1.931
And the expected persistent files created with the old Tails version are present in the filesystem 0.844
And all persistent directories from the old Tails version have safe access rights 1.431
After features/support/hooks.rb:339 0.905
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.426
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.878
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.275
When the network is plugged 0.023
And Tor is ready 13.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.783
Given I shutdown Tails and wait for the computer to power off 5.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.437
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.095
# 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.150
When the network is plugged 0.032
And Tor is ready 10.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.888
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.982
Given I shutdown Tails and wait for the computer to power off 3.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.626
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.246
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.034
And Tor is ready 9.929
Then the Upgrader considers the system as up-to-date 10.403
# 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 3.412
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.684
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 7.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.647
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.000