Project Number Date
test_Tails_ISO_stable 6729 08 Oct 2026, 07:33

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:53.112 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:9.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.657
When I start Tails from USB drive "old" with network unplugged 51.473
Then the boot device has safe access rights 2.525
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.476
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.288
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 49.826
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 30.039
And I take note of which tps features are available 7.923
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 2.632
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.006
Tags: @product
1:47.490
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.633
Then Tails is running from USB drive "old" 0.238
And all tps features are active 9.149
When I write some files expected to persist 1.169
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.757
And I take note of which tps features are available 10.928
And I shutdown Tails and wait for the computer to power off 4.599
# 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.348
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.890
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.916
And I log in to a new session 12.131
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.008
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.903
Then the running Tails is installed on USB drive "to_upgrade" 19.361
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:339 3.849
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.318
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.016
Then all tps features from the old Tails version are active 0.981
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.282
And the expected persistent files created with the old Tails version are present in the filesystem 0.830
And all persistent directories from the old Tails version have safe access rights 1.779
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.145
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 8.409
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.023
And Tor is ready 12.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.940
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.599
Given I shutdown Tails and wait for the computer to power off 5.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.506
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 8.593
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.225
When the network is plugged 0.027
And Tor is ready 10.459
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.219
Given I shutdown Tails and wait for the computer to power off 4.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.272
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.031
And Tor is ready 10.274
Then the Upgrader considers the system as up-to-date 0.109
# 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 3.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.432
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.382
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.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.907
After features/support/hooks.rb:339 0.755
After features/support/hooks.rb:108 0.000