Project Number Date
test_Tails_ISO_devel 4668 09 Oct 2026, 11:24

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:4.968 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:0.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.332
When I start Tails from USB drive "old" with network unplugged 43.800
Then the boot device has safe access rights 2.214
And Tails is running from USB drive "old" 0.165
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.135
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.564
After features/support/hooks.rb:108 0.011
Tags: @product
1:21.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login 48.474
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 21.816
And I take note of which tps features are available 6.269
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 4.146
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.521
Then Tails is running from USB drive "old" 0.281
And all tps features are active 7.086
When I write some files expected to persist 1.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.584
And I take note of which tps features are available 5.800
And I shutdown Tails and wait for the computer to power off 2.665
# 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.674
After features/support/hooks.rb:339 0.528
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.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 without a persistent partition and stopped at Tails Greeter's login screen 8.335
And I log in to a new session 11.302
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.038
Then the running Tails is installed on USB drive "to_upgrade" 18.097
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.106
After features/support/hooks.rb:339 1.632
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.155
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.361
Then all tps features from the old Tails version are active 1.139
And Tails is running from USB drive "to_upgrade" 0.202
And the boot device has safe access rights 2.048
And the expected persistent files created with the old Tails version are present in the filesystem 0.823
And all persistent directories from the old Tails version have safe access rights 1.477
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.059
Tags: @product @automatic_upgrade
3:32.153
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.243
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.033
And Tor is ready 11.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.522
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.852
Given I shutdown Tails and wait for the computer to power off 5.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.806
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.242
When the network is plugged 0.035
And Tor is ready 10.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.847
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.398
Given I shutdown Tails and wait for the computer to power off 4.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.564
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.283
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.025
And Tor is ready 11.055
Then the Upgrader considers the system as up-to-date 0.090
# 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.728
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:339 0.818
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.917
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.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 8.284
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.585
After features/support/hooks.rb:339 0.822
After features/support/hooks.rb:108 0.000