Project Number Date
test_Tails_ISO_devel 4616 14 Sep 2026, 18:34

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:27.471 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:17.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.653
When I start Tails from USB drive "old" with network unplugged 1:0.052
Then the boot device has safe access rights 2.192
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 1.627
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 48.179
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 23.484
And I take note of which tps features are available 5.728
Then a Tails persistence partition exists on USB drive "old" 0.657
And I shutdown Tails and wait for the computer to power off 4.017
After features/support/hooks.rb:339 0.455
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.660
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.110
When I write some files expected to persist 0.863
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.107
And all persistence configuration files have safe access rights 0.219
And all persistent directories from the old Tails version have safe access rights 1.256
And I take note of which tps features are available 5.898
And I shutdown Tails and wait for the computer to power off 2.554
# 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" 11.096
After features/support/hooks.rb:339 0.143
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.970
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.337
And I log in to a new session 10.882
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.606
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.446
Then the running Tails is installed on USB drive "to_upgrade" 18.230
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.224
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 2.034
And the expected persistent files created with the old Tails version are present in the filesystem 0.890
And all persistent directories from the old Tails version have safe access rights 1.399
After features/support/hooks.rb:339 0.727
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:40.978
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.013
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.034
And Tor is ready 11.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.970
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.127
Given I shutdown Tails and wait for the computer to power off 5.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.299
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.393
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.198
When the network is plugged 0.025
And Tor is ready 10.422
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.455
Given I shutdown Tails and wait for the computer to power off 4.014
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.254
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.416
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.027
And Tor is ready 10.236
Then the Upgrader considers the system as up-to-date 10.430
# 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.191
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.281
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.060
Tags: @product @automatic_upgrade
18.328
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.023
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 8.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.875
After features/support/hooks.rb:339 0.865
After features/support/hooks.rb:108 0.000