Project Number Date
test_Tails_ISO_stable 6653 09 Sep 2026, 19:34

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:52.155 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:8.291
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.010
When I start Tails from USB drive "old" with network unplugged 50.359
Then the boot device has safe access rights 2.168
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 2.110
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.560
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 50.228
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 24.445
And I take note of which tps features are available 6.865
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 4.132
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.013
Tags: @product
1:35.084
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.547
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.470
When I write some files expected to persist 1.048
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 1.876
And I take note of which tps features are available 6.620
And I shutdown Tails and wait for the computer to power off 2.674
# 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.982
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.139
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 8.537
And I log in to a new session 13.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.802
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.882
Then the running Tails is installed on USB drive "to_upgrade" 19.216
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:339 2.132
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.446
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.799
Then all tps features from the old Tails version are active 1.172
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.479
And the expected persistent files created with the old Tails version are present in the filesystem 1.034
And all persistent directories from the old Tails version have safe access rights 1.614
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.785
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.516
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.036
And Tor is ready 12.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.940
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.412
Given I shutdown Tails and wait for the computer to power off 5.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.761
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.782
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
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.197
# 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.225
When the network is plugged 0.091
And Tor is ready 10.385
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.637
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.848
Given I shutdown Tails and wait for the computer to power off 2.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.024
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.032
And Tor is ready 11.324
Then the Upgrader considers the system as up-to-date 0.090
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.533
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
34.846
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.773
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 9.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.096
After features/support/hooks.rb:339 1.054
After features/support/hooks.rb:108 0.000