Project Number Date
test_Tails_ISO_devel 4335 11 Apr 2026, 11:29

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:1.321 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:12.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.122
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.703
When I start Tails from USB drive "old" with network unplugged 51.313
Then the boot device has safe access rights 3.146
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.577
After features/support/hooks.rb:100 0.019
Tags: @product
1:33.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login 57.418
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 25.092
And I take note of which tps features are available 1.222
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:331 0.280
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.079
Then Tails is running from USB drive "old" 0.266
And all tps features are active 1.328
When I write some files expected to persist 1.772
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.305
And I take note of which tps features are available 0.214
And I shutdown Tails and wait for the computer to power off 8.449
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.251
After features/support/hooks.rb:331 0.410
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.466
And I log in to a new session 17.875
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.737
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.302
Then the running Tails is installed on USB drive "to_upgrade" 16.694
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 3.184
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.589
Then all tps features from the old Tails version are active 1.153
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.874
And the expected persistent files created with the old Tails version are present in the filesystem 1.382
And all persistent directories from the old Tails version have safe access rights 2.254
After features/support/hooks.rb:331 0.781
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:40.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.186
And no SquashFS delta is installed 0.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.016
And Tor is ready 23.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.095
Given I shutdown Tails and wait for the computer to power off 21.294
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.481
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.205
When the network is plugged 0.016
And Tor is ready 22.950
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.814
Given I shutdown Tails and wait for the computer to power off 17.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.879
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.016
And Tor is ready 20.800
Then the Upgrader considers the system as up-to-date 0.130
# 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.418
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
29.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.011
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 20.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
After features/support/hooks.rb:331 1.093
After features/support/hooks.rb:100 0.000