Project Number Date
test_Tails_ISO_stable 6434 08 Jun 2026, 11:30

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:2.151 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
59.523
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
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 42.083
Then the boot device has safe access rights 2.721
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 1.344
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.644
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 52.914
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 23.656
And I take note of which tps features are available 0.351
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 7.880
After features/support/hooks.rb:335 0.205
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.458
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.070
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.080
When I write some files expected to persist 1.334
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 7.959
# 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.033
After features/support/hooks.rb:335 0.370
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.011
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 without a persistent partition and stopped at Tails Greeter's login screen 8.067
And I log in to a new session 11.465
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.159
Then the running Tails is installed on USB drive "to_upgrade" 15.010
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:335 2.059
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.489
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.745
Then all tps features from the old Tails version are active 0.866
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.072
And all persistent directories from the old Tails version have safe access rights 2.074
After features/support/hooks.rb:335 0.789
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:35.447
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.192
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
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.417
When the network is plugged 0.014
And Tor is ready 12.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.516
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.833
Given I shutdown Tails and wait for the computer to power off 10.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.959
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.183
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.201
When the network is plugged 0.016
And Tor is ready 9.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.684
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.101
Given I shutdown Tails and wait for the computer to power off 7.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.315
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.315
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.013
And Tor is ready 9.715
Then the Upgrader considers the system as up-to-date 10.491
# 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.823
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:335 0.930
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.575
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 7.487
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
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.064
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.022
After features/support/hooks.rb:335 0.603
After features/support/hooks.rb:104 0.000