Project Number Date
test_Tails_ISO_devel 4451 16 Jun 2026, 14:07

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:27.808 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:1.725
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.282
When I start Tails from USB drive "old" with network unplugged 42.684
Then the boot device has safe access rights 2.895
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 1.338
After features/support/hooks.rb:108 0.009
Tags: @product
1:33.680
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 54.845
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 25.112
And I take note of which tps features are available 4.290
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.499
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.009
Tags: @product
1:45.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.210
Then Tails is running from USB drive "old" 0.294
And all tps features are active 5.867
When I write some files expected to persist 1.529
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.343
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.353
And I take note of which tps features are available 4.673
And I shutdown Tails and wait for the computer to power off 8.109
# 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" 13.583
After features/support/hooks.rb:339 0.419
After features/support/hooks.rb:108 0.011
Tags: @product
2:14.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.376
And I log in to a new session 14.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.368
Then the running Tails is installed on USB drive "to_upgrade" 16.624
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:339 2.184
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.474
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.544
Then all tps features from the old Tails version are active 1.153
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.911
And the expected persistent files created with the old Tails version are present in the filesystem 1.316
And all persistent directories from the old Tails version have safe access rights 2.173
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:10.156
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.517
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.013
And Tor is ready 13.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.585
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.453
Given I shutdown Tails and wait for the computer to power off 9.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.011
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 6.050
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.253
When the network is plugged 0.022
And Tor is ready 10.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.717
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.020
Given I shutdown Tails and wait for the computer to power off 4.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.126
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.021
And Tor is ready 10.517
Then the Upgrader considers the system as up-to-date 10.626
# 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 5.003
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:339 1.081
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
23.416
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 with a persistent partition enabled and logged in 8.966
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.048
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.000