Project Number Date
test_Tails_ISO_devel 4486 09 Jul 2026, 07:56

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:0.829 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.993
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 13.440
When I start Tails from USB drive "old" with network unplugged 51.911
Then the boot device has safe access rights 2.835
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.581
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.926
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.142
And I start Tails from USB drive "old" with network unplugged and I login 53.700
Then Tails is running from USB drive "old" 0.212
And I create a persistent partition 24.611
And I take note of which tps features are available 4.392
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 4.323
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.126
Then Tails is running from USB drive "old" 0.235
And all tps features are active 4.877
When I write some files expected to persist 1.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.289
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 4.085
And I shutdown Tails and wait for the computer to power off 8.101
# 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.212
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.567
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 7.908
And I log in to a new session 13.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.498
Then the running Tails is installed on USB drive "to_upgrade" 14.712
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:339 2.104
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.279
Then all tps features from the old Tails version are active 1.083
And Tails is running from USB drive "to_upgrade" 0.276
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.095
And all persistent directories from the old Tails version have safe access rights 1.830
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:58.272
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.275
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.016
And Tor is ready 13.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.122
Given I shutdown Tails and wait for the computer to power off 11.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.107
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 5.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.209
# 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.215
When the network is plugged 0.023
And Tor is ready 10.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.272
Given I shutdown Tails and wait for the computer to power off 8.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.074
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.013
And Tor is ready 9.813
Then the Upgrader considers the system as up-to-date 10.557
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.969
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 7.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
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.056
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 8.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.072
After features/support/hooks.rb:339 0.781
After features/support/hooks.rb:108 0.000