Project Number Date
test_Tails_ISO_stable 6421 03 Jun 2026, 11:43

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:37.811 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:0.643
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.336
When I start Tails from USB drive "old" with network unplugged 42.812
Then the boot device has safe access rights 2.764
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:335 3.481
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.774
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 55.431
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 25.730
And I take note of which tps features are available 0.382
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 8.272
After features/support/hooks.rb:335 0.662
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.237
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.855
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.098
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.790
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.084
# 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.202
After features/support/hooks.rb:335 0.590
After features/support/hooks.rb:104 0.006
Tags: @product
2:12.675
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.323
And I log in to a new session 12.924
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.965
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.371
Then the running Tails is installed on USB drive "to_upgrade" 15.540
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:335 2.106
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.968
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.905
Then all tps features from the old Tails version are active 0.900
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.651
And the expected persistent files created with the old Tails version are present in the filesystem 1.143
And all persistent directories from the old Tails version have safe access rights 2.042
After features/support/hooks.rb:335 0.934
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:53.403
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.439
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
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.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.016
And Tor is ready 13.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.369
Given I shutdown Tails and wait for the computer to power off 9.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.954
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.228
When the network is plugged 0.033
And Tor is ready 20.758
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.830
Given I shutdown Tails and wait for the computer to power off 8.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.908
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.194
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.020
And Tor is ready 11.343
Then the Upgrader considers the system as up-to-date 10.605
# 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.150
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:335 1.031
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.108
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.402
After features/support/hooks.rb:335 0.639
After features/support/hooks.rb:104 0.000