Project Number Date
test_Tails_ISO_stable 6565 07 Aug 2026, 11: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 11:20.471 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:6.088
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 12.959
When I start Tails from USB drive "old" with network unplugged 49.469
Then the boot device has safe access rights 1.995
And Tails is running from USB drive "old" 0.174
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.436
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.497
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 22.619
And I take note of which tps features are available 6.425
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 4.041
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.725
Then Tails is running from USB drive "old" 0.208
And all tps features are active 7.566
When I write some files expected to persist 1.074
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.656
And I take note of which tps features are available 5.881
And I shutdown Tails and wait for the computer to power off 2.547
# 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.621
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.075
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 without a persistent partition and stopped at Tails Greeter's login screen 8.307
And I log in to a new session 11.454
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.094
Then the running Tails is installed on USB drive "to_upgrade" 18.003
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 0.727
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.894
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.135
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.825
Then all tps features from the old Tails version are active 1.155
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.166
And the expected persistent files created with the old Tails version are present in the filesystem 0.931
And all persistent directories from the old Tails version have safe access rights 1.399
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:39.655
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 8.106
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.270
When the network is plugged 0.034
And Tor is ready 11.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.978
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.816
Given I shutdown Tails and wait for the computer to power off 5.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.914
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 7.407
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.242
When the network is plugged 0.024
And Tor is ready 10.443
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.512
Given I shutdown Tails and wait for the computer to power off 3.964
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.351
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.727
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.033
And Tor is ready 10.033
Then the Upgrader considers the system as up-to-date 10.433
# 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.161
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.283
After features/support/hooks.rb:339 0.641
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.461
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.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 9.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.457
After features/support/hooks.rb:339 0.669
After features/support/hooks.rb:108 0.000