Project Number Date
test_Tails_ISO_stable 6562 05 Aug 2026, 23:10

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:46.915 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:1.493
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.757
When I start Tails from USB drive "old" with network unplugged 43.987
Then the boot device has safe access rights 2.048
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.416
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.627
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 49.972
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 23.428
And I take note of which tps features are available 6.316
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 4.085
After features/support/hooks.rb:339 0.219
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.209
Then Tails is running from USB drive "old" 0.237
And all tps features are active 7.574
When I write some files expected to persist 1.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.465
And I take note of which tps features are available 5.965
And I shutdown Tails and wait for the computer to power off 4.107
# 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.435
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.016
Tags: @product
2:12.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.678
And I log in to a new session 11.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.660
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.901
Then the running Tails is installed on USB drive "to_upgrade" 18.689
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.606
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.107
And the expected persistent files created with the old Tails version are present in the filesystem 1.056
And all persistent directories from the old Tails version have safe access rights 1.794
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:51.504
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 with a persistent partition enabled and logged in 21.461
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.024
And Tor is ready 12.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.889
Given I shutdown Tails and wait for the computer to power off 5.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.658
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.631
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.169
When the network is plugged 0.025
And Tor is ready 10.482
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.950
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.992
Given I shutdown Tails and wait for the computer to power off 4.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.717
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.353
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.146
When the network is plugged 0.028
And Tor is ready 10.325
Then the Upgrader considers the system as up-to-date 0.111
# 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.590
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
32.016
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 21.150
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.543
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.958
After features/support/hooks.rb:339 0.664
After features/support/hooks.rb:108 0.000