Project Number Date
test_Tails_ISO_stable 6209 16 Mar 2026, 16:45

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 12:28.740 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:4.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.159
When I start Tails from USB drive "old" with network unplugged 45.279
Then the boot device has safe access rights 2.990
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.868
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.354
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.638
And I take note of which tps features are available 0.766
Then a Tails persistence partition exists on USB drive "old" 0.634
And I shutdown Tails and wait for the computer to power off 8.396
After features/support/hooks.rb:331 0.220
After features/support/hooks.rb:100 0.010
Tags: @product
1:29.844
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.670
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.186
When I write some files expected to persist 1.478
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 2.233
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 8.362
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.698
After features/support/hooks.rb:331 0.528
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.933
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.701
And I log in to a new session 11.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.010
And I plug USB drive "to_upgrade" 2.268
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.503
Then the running Tails is installed on USB drive "to_upgrade" 16.585
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 2.051
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.222
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.914
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 1.917
After features/support/hooks.rb:331 0.600
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:32.173
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.072
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.019
And Tor is ready 21.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.359
Given I shutdown Tails and wait for the computer to power off 14.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.120
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.196
When the network is plugged 0.020
And Tor is ready 20.604
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.368
Given I shutdown Tails and wait for the computer to power off 17.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.012
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.027
And Tor is ready 20.306
Then the Upgrader considers the system as up-to-date 0.095
# 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.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:331 0.790
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
27.696
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 7.824
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.263
And Tor is ready 18.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.000