Project Number Date
test_Tails_ISO_stable 6476 30 Jun 2026, 07:37

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:10.617 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:15.392
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.144
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.403
When I start Tails from USB drive "old" with network unplugged 56.361
Then the boot device has safe access rights 2.771
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 3.723
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.267
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.962
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 25.710
And I take note of which tps features are available 4.425
Then a Tails persistence partition exists on USB drive "old" 0.574
And I shutdown Tails and wait for the computer to power off 8.218
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.397
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.551
Then Tails is running from USB drive "old" 0.246
And all tps features are active 5.363
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 1.820
And I take note of which tps features are available 3.747
And I shutdown Tails and wait for the computer to power off 8.241
# 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.340
After features/support/hooks.rb:339 0.420
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.317
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.225
And I log in to a new session 11.923
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.821
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.449
Then the running Tails is installed on USB drive "to_upgrade" 14.381
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.127
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.642
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.185
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.609
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.149
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:57.994
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.244
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.015
And Tor is ready 12.897
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.448
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.629
Given I shutdown Tails and wait for the computer to power off 11.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.307
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.197
When the network is plugged 0.015
And Tor is ready 10.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.442
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.837
Given I shutdown Tails and wait for the computer to power off 8.069
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.585
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.597
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.018
And Tor is ready 12.133
Then the Upgrader considers the system as up-to-date 10.583
# 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.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:339 1.094
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.605
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 7.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.593
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.875
After features/support/hooks.rb:339 0.614
After features/support/hooks.rb:108 0.000