Project Number Date
test_Tails_ISO_devel 4524 30 Jul 2026, 22:05

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:36.466 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:4.876
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 13.695
When I start Tails from USB drive "old" with network unplugged 47.197
Then the boot device has safe access rights 2.244
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.680
After features/support/hooks.rb:108 0.007
Tags: @product
1:26.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 47.789
Then Tails is running from USB drive "old" 0.163
And I create a persistent partition 25.056
And I take note of which tps features are available 7.265
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 5.137
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.185
Then Tails is running from USB drive "old" 0.245
And all tps features are active 7.804
When I write some files expected to persist 1.053
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.612
And I take note of which tps features are available 6.146
And I shutdown Tails and wait for the computer to power off 2.661
# 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.576
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.829
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.343
And I log in to a new session 12.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.810
And I plug USB drive "to_upgrade" 2.188
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.433
Then the running Tails is installed on USB drive "to_upgrade" 18.728
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:339 4.230
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.078
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.127
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.554
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.660
And the expected persistent files created with the old Tails version are present in the filesystem 1.238
And all persistent directories from the old Tails version have safe access rights 2.102
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.810
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.451
And no SquashFS delta is installed 0.056
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.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.035
And Tor is ready 14.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.111
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.950
Given I shutdown Tails and wait for the computer to power off 7.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.917
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.585
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.083
# 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.165
When the network is plugged 0.035
And Tor is ready 10.579
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.515
Given I shutdown Tails and wait for the computer to power off 2.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.444
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 9.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.028
And Tor is ready 10.958
Then the Upgrader considers the system as up-to-date 0.085
# 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.885
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 1.121
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.898
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.418
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.035
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 10.378
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.764
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.000