Project Number Date
test_Tails_ISO_stable 6448 16 Jun 2026, 13:19

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 13:10.209 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:16.164
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.028
Given a computer 0.274
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.915
When I start Tails from USB drive "old" with network unplugged 56.692
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.145
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.295
After features/support/hooks.rb:339 1.602
After features/support/hooks.rb:108 0.025
Tags: @product
1:36.604
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.041
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 57.941
Then Tails is running from USB drive "old" 0.551
And I create a persistent partition 25.196
And I take note of which tps features are available 4.973
Then a Tails persistence partition exists on USB drive "old" 0.574
And I shutdown Tails and wait for the computer to power off 7.154
After features/support/hooks.rb:339 0.284
After features/support/hooks.rb:108 0.017
Tags: @product
1:45.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.738
Then Tails is running from USB drive "old" 0.229
And all tps features are active 5.575
When I write some files expected to persist 1.444
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 2.786
And I take note of which tps features are available 4.603
And I shutdown Tails and wait for the computer to power off 4.450
# 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.869
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.018
Tags: @product
2:16.158
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.710
And I log in to a new session 14.288
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.795
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.426
Then the running Tails is installed on USB drive "to_upgrade" 17.270
And I unplug USB drive "to_upgrade" 0.289
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:339 3.414
After features/support/hooks.rb:108 0.000
Tags: @product
1:25.445
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.721
Then all tps features from the old Tails version are active 1.903
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.154
And the expected persistent files created with the old Tails version are present in the filesystem 1.822
And all persistent directories from the old Tails version have safe access rights 2.458
After features/support/hooks.rb:339 0.950
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
4:27.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.989
And no SquashFS delta is installed 0.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.017
And Tor is ready 14.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.729
Given I shutdown Tails and wait for the computer to power off 10.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.166
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.279
When the network is plugged 0.029
And Tor is ready 10.309
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.202
Given I shutdown Tails and wait for the computer to power off 7.483
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.089
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 6.205
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.018
And Tor is ready 10.932
Then the Upgrader considers the system as up-to-date 10.532
# 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 5.276
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.055
Tags: @product @automatic_upgrade
22.740
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.488
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.000