Project Number Date
test_Tails_ISO_devel 4637 26 Sep 2026, 11:27

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 13:29.015 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.721
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.341
When I start Tails from USB drive "old" with network unplugged 47.092
Then the boot device has safe access rights 2.484
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.808
After features/support/hooks.rb:108 0.007
Tags: @product
1:20.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 47.264
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 23.516
And I take note of which tps features are available 6.520
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 2.756
After features/support/hooks.rb:339 0.472
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.608
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.940
When I write some files expected to persist 0.961
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.242
And all persistent directories from the old Tails version have safe access rights 1.577
And I take note of which tps features are available 6.267
And I shutdown Tails and wait for the computer to power off 2.603
# 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.244
After features/support/hooks.rb:339 0.374
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.312
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.521
And I log in to a new session 12.887
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.565
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.818
Then the running Tails is installed on USB drive "to_upgrade" 17.988
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.693
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.235
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.749
Then all tps features from the old Tails version are active 1.147
And Tails is running from USB drive "to_upgrade" 0.165
And the boot device has safe access rights 1.990
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 1.881
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
5:47.437
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.454
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.163
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.164
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.268
When the network is plugged 0.036
And Tor is ready 11.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:5.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.797
Given I shutdown Tails and wait for the computer to power off 5.224
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.344
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.010
And the file system changes introduced in version 6.2~testoverlayfs are present 0.169
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.078
# 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.158
When the network is plugged 0.039
And Tor is ready 10.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.771
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.503
Given I shutdown Tails and wait for the computer to power off 2.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.929
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.622
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.022
And Tor is ready 10.262
Then the Upgrader considers the system as up-to-date 10.435
# 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.394
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
23.560
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.969
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 10.245
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.984
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.000