Project Number Date
test_Tails_ISO_devel 4550 15 Aug 2026, 11:23

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:55.702 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.046
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.675
When I start Tails from USB drive "old" with network unplugged 39.429
Then the boot device has safe access rights 2.173
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.499
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.224
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 48.094
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.369
And I take note of which tps features are available 6.540
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 4.311
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.010
Tags: @product
1:36.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.222
Then Tails is running from USB drive "old" 0.276
And all tps features are active 7.614
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 6.835
And I shutdown Tails and wait for the computer to power off 4.113
# 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.792
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.828
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.976
And I log in to a new session 12.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.627
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.993
Then the running Tails is installed on USB drive "to_upgrade" 19.011
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.756
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.791
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.129
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.447
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.166
And the boot device has safe access rights 2.178
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 1.681
After features/support/hooks.rb:339 0.939
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
5:1.330
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.616
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.310
When the network is plugged 0.023
And Tor is ready 12.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.700
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.850
Given I shutdown Tails and wait for the computer to power off 5.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.805
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.837
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# 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.211
When the network is plugged 0.025
And Tor is ready 40.693
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.303
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.731
Given I shutdown Tails and wait for the computer to power off 2.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.858
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.393
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.026
And Tor is ready 1:10.093
Then the Upgrader considers the system as up-to-date 0.123
# 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.049
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.575
After features/support/hooks.rb:339 0.706
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
31.880
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 21.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.027
And Tor is ready 9.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.905
After features/support/hooks.rb:339 0.829
After features/support/hooks.rb:108 0.000