Project Number Date
test_Tails_ISO_stable-flatpak 18 15 Sep 2026, 19:53

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:30.548 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
57.009
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
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.513
When I start Tails from USB drive "old" with network unplugged 39.251
Then the boot device has safe access rights 2.485
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.470
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.170
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 48.798
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 24.849
And I take note of which tps features are available 6.608
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 4.079
After features/support/hooks.rb:339 0.159
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.279
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.775
Then Tails is running from USB drive "old" 0.310
And all tps features are active 7.788
When I write some files expected to persist 1.336
# 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.279
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 6.296
And I shutdown Tails and wait for the computer to power off 4.118
# 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.180
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.225
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.293
And I log in to a new session 13.099
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.751
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.593
Then the running Tails is installed on USB drive "to_upgrade" 18.004
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.738
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.427
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.654
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 2.214
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 2.113
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:48.846
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.201
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.255
When the network is plugged 0.033
And Tor is ready 12.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.474
Given I shutdown Tails and wait for the computer to power off 5.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.198
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.180
When the network is plugged 0.034
And Tor is ready 10.454
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.870
Given I shutdown Tails and wait for the computer to power off 3.955
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.084
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.319
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.046
And Tor is ready 10.234
Then the Upgrader considers the system as up-to-date 10.414
# 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.538
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 1.050
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
19.590
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.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.793
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.000