Project Number Date
test_Tails_ISO_stable 6369 11 May 2026, 21:20

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:15.998 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:18.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.411
When I start Tails from USB drive "old" with network unplugged 59.126
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 3.713
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 58.310
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 25.219
And I take note of which tps features are available 0.810
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 8.548
After features/support/hooks.rb:331 0.184
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.394
Then Tails is running from USB drive "old" 0.455
And all tps features are active 1.234
When I write some files expected to persist 1.534
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.509
And all persistent directories from the old Tails version have safe access rights 2.175
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.039
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.282
After features/support/hooks.rb:331 0.244
After features/support/hooks.rb:100 0.013
Tags: @product
2:13.689
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.288
And I log in to a new session 13.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.876
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.009
Then the running Tails is installed on USB drive "to_upgrade" 16.317
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.758
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.206
And all persistent directories from the old Tails version have safe access rights 2.239
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
4:54.644
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 with a persistent partition enabled and logged in 9.332
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.040
And Tor is ready 23.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.221
Given I shutdown Tails and wait for the computer to power off 20.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.844
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.295
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.209
When the network is plugged 0.015
And Tor is ready 21.554
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.811
Given I shutdown Tails and wait for the computer to power off 17.725
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.674
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 1.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.015
And Tor is ready 21.631
Then the Upgrader considers the system as up-to-date 0.152
# 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 4.853
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:331 0.864
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
27.052
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.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 18.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.437
After features/support/hooks.rb:331 0.763
After features/support/hooks.rb:100 0.000