Project Number Date
test_Tails_ISO_stable 6571 10 Aug 2026, 13:34

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:57.248 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:11.716
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.503
When I start Tails from USB drive "old" with network unplugged 52.583
Then the boot device has safe access rights 2.675
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.879
After features/support/hooks.rb:108 0.008
Tags: @product
1:31.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login 52.002
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 27.021
And I take note of which tps features are available 7.726
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 3.950
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.762
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.939
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.961
When I write some files expected to persist 1.310
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.144
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.835
And I take note of which tps features are available 6.368
And I shutdown Tails and wait for the computer to power off 3.890
# 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.697
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.005
Tags: @product
2:16.862
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.238
And I log in to a new session 13.252
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.333
Then the running Tails is installed on USB drive "to_upgrade" 19.681
And I unplug USB drive "to_upgrade" 0.109
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:339 3.867
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.354
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.191
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.606
And the expected persistent files created with the old Tails version are present in the filesystem 1.157
And all persistent directories from the old Tails version have safe access rights 1.998
After features/support/hooks.rb:339 0.832
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:45.942
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.527
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.031
And Tor is ready 12.995
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.192
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.911
Given I shutdown Tails and wait for the computer to power off 5.765
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.907
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.037
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
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.108
# 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.199
When the network is plugged 0.025
And Tor is ready 9.635
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.692
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.975
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.907
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.025
And Tor is ready 10.891
Then the Upgrader considers the system as up-to-date 0.091
# 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.645
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.004
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 8.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.267
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.000