Project Number Date
test_Tails_ISO_stable-flatpak 47 15 Oct 2026, 19:39

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:1.745 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:2.686
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.528
When I start Tails from USB drive "old" with network unplugged 45.632
Then the boot device has safe access rights 1.711
And Tails is running from USB drive "old" 0.161
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:339 3.381
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.989
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 46.925
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.086
And I take note of which tps features are available 6.096
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 4.042
After features/support/hooks.rb:339 0.313
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.278
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.739
Then Tails is running from USB drive "old" 0.196
And all tps features are active 6.809
When I write some files expected to persist 1.146
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.148
And all persistence configuration files have safe access rights 0.209
And all persistent directories from the old Tails version have safe access rights 1.846
And I take note of which tps features are available 5.901
And I shutdown Tails and wait for the computer to power off 3.911
# 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.228
After features/support/hooks.rb:339 0.523
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.693
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.163
And I log in to a new session 9.987
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.583
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.647
Then the running Tails is installed on USB drive "to_upgrade" 17.867
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.696
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 1.745
And the expected persistent files created with the old Tails version are present in the filesystem 1.021
And all persistent directories from the old Tails version have safe access rights 1.712
After features/support/hooks.rb:339 0.578
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.360
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.932
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
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.192
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.046
And Tor is ready 12.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.913
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.285
Given I shutdown Tails and wait for the computer to power off 6.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.033
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# 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.187
When the network is plugged 0.025
And Tor is ready 10.234
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.453
Given I shutdown Tails and wait for the computer to power off 5.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.530
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.364
And the file system changes introduced in version 6.3~testoverlayfs are present 0.278
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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.036
And Tor is ready 10.194
Then the Upgrader considers the system as up-to-date 0.098
# 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.506
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.297
After features/support/hooks.rb:339 0.988
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.146
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 7.809
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.049
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.000