Project Number Date
test_Tails_ISO_devel 4365 29 Apr 2026, 11:25

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:39.580 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:6.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 14.640
When I start Tails from USB drive "old" with network unplugged 46.775
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:331 3.799
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 58.720
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 26.762
And I take note of which tps features are available 0.839
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 8.473
After features/support/hooks.rb:331 0.655
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.848
Then Tails is running from USB drive "old" 0.266
And all tps features are active 1.382
When I write some files expected to persist 1.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.272
And I take note of which tps features are available 0.240
And I shutdown Tails and wait for the computer to power off 3.103
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.137
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.104
And I log in to a new session 16.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.956
And I plug USB drive "to_upgrade" 2.328
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.215
Then the running Tails is installed on USB drive "to_upgrade" 17.194
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 2.651
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.081
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.821
Then all tps features from the old Tails version are active 0.904
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.266
And all persistent directories from the old Tails version have safe access rights 2.136
After features/support/hooks.rb:331 0.651
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
5:5.984
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.949
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.034
And Tor is ready 25.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.775
Given I shutdown Tails and wait for the computer to power off 11.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.075
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.195
When the network is plugged 0.013
And Tor is ready 41.425
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.569
Given I shutdown Tails and wait for the computer to power off 17.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.474
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.287
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.019
And Tor is ready 21.023
Then the Upgrader considers the system as up-to-date 0.106
# 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.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:331 1.217
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
49.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.893
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 41.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 0.895
After features/support/hooks.rb:100 0.000