Project Number Date
test_Tails_ISO_stable 6326 23 Apr 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 13:28.399 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:6.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.723
When I start Tails from USB drive "old" with network unplugged 46.053
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.457
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.636
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 57.384
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 25.780
And I take note of which tps features are available 0.835
Then a Tails persistence partition exists on USB drive "old" 0.618
And I shutdown Tails and wait for the computer to power off 8.087
After features/support/hooks.rb:331 0.273
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.946
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.404
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.305
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 8.038
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.427
After features/support/hooks.rb:331 0.350
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.348
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.398
And I log in to a new session 15.317
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.290
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.572
Then the running Tails is installed on USB drive "to_upgrade" 17.677
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:331 2.434
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.648
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.216
And all persistent directories from the old Tails version have safe access rights 1.961
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:5.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.738
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.383
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.021
And Tor is ready 23.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.803
Given I shutdown Tails and wait for the computer to power off 21.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.851
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.541
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.287
When the network is plugged 0.014
And Tor is ready 21.947
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.717
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.202
Given I shutdown Tails and wait for the computer to power off 17.836
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.155
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.365
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.261
When the network is plugged 0.023
And Tor is ready 22.975
Then the Upgrader considers the system as up-to-date 0.140
# 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.869
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.569
After features/support/hooks.rb:331 0.832
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
30.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 20.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
After features/support/hooks.rb:331 0.827
After features/support/hooks.rb:100 0.000