Project Number Date
test_Tails_ISO_devel 4613 13 Sep 2026, 11:11

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 10:37.418 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
57.898
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.221
When I start Tails from USB drive "old" with network unplugged 41.012
Then the boot device has safe access rights 1.975
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 3.637
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.970
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 45.073
Then Tails is running from USB drive "old" 0.188
And I create a persistent partition 22.915
And I take note of which tps features are available 6.303
Then a Tails persistence partition exists on USB drive "old" 0.450
And I shutdown Tails and wait for the computer to power off 3.959
After features/support/hooks.rb:339 0.327
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.293
Then Tails is running from USB drive "old" 0.149
And all tps features are active 6.793
When I write some files expected to persist 0.975
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.218
And all persistent directories from the old Tails version have safe access rights 1.410
And I take note of which tps features are available 6.112
And I shutdown Tails and wait for the computer to power off 2.528
# 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" 10.916
After features/support/hooks.rb:339 0.138
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.697
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.152
And I log in to a new session 10.812
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.680
And I plug USB drive "to_upgrade" 2.194
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.919
Then the running Tails is installed on USB drive "to_upgrade" 17.716
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.301
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.990
Then all tps features from the old Tails version are active 0.996
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 1.842
And the expected persistent files created with the old Tails version are present in the filesystem 0.796
And all persistent directories from the old Tails version have safe access rights 1.397
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:18.875
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.130
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.267
When the network is plugged 0.034
And Tor is ready 11.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.988
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.576
Given I shutdown Tails and wait for the computer to power off 5.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.141
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.185
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.161
When the network is plugged 0.035
And Tor is ready 10.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.885
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.082
Given I shutdown Tails and wait for the computer to power off 2.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.455
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.283
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.072
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.027
And Tor is ready 10.231
Then the Upgrader considers the system as up-to-date 0.103
# 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.030
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.293
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
19.011
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.721
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.871
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.000