Project Number Date
test_Tails_ISO_devel 4302 29 Mar 2026, 11:41

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 12:46.205 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:16.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.703
When I start Tails from USB drive "old" with network unplugged 57.991
Then the boot device has safe access rights 2.858
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.290
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 56.630
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 22.326
And I take note of which tps features are available 0.660
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 8.086
After features/support/hooks.rb:331 0.537
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.461
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.041
When I write some files expected to persist 1.342
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 4.038
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.151
After features/support/hooks.rb:331 0.445
After features/support/hooks.rb:100 0.006
Tags: @product
2:24.242
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 without a persistent partition and stopped at Tails Greeter's login screen 8.120
And I log in to a new session 18.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.956
And I plug USB drive "to_upgrade" 2.746
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.906
Then the running Tails is installed on USB drive "to_upgrade" 14.829
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:331 10.923
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.382
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 1.971
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:30.548
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 with a persistent partition enabled and logged in 9.102
And no SquashFS delta is installed 0.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.015
And Tor is ready 26.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.465
Given I shutdown Tails and wait for the computer to power off 18.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.408
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.048
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
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.131
# 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.183
When the network is plugged 0.015
And Tor is ready 20.234
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.405
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.894
Given I shutdown Tails and wait for the computer to power off 13.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.531
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.014
And Tor is ready 20.109
Then the Upgrader considers the system as up-to-date 0.112
# 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.126
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:331 0.926
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
32.482
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 7.757
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 24.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.000