Project Number Date
test_Tails_ISO_devel 4568 26 Aug 2026, 11:18

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:24.183 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
57.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.118
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.744
When I start Tails from USB drive "old" with network unplugged 39.756
Then the boot device has safe access rights 2.204
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.661
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 50.033
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 24.155
And I take note of which tps features are available 7.525
Then a Tails persistence partition exists on USB drive "old" 0.637
And I shutdown Tails and wait for the computer to power off 2.760
After features/support/hooks.rb:339 0.374
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.901
Then Tails is running from USB drive "old" 0.239
And all tps features are active 7.598
When I write some files expected to persist 1.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.224
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 6.926
And I shutdown Tails and wait for the computer to power off 2.620
# 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" 12.123
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.287
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.649
And I log in to a new session 12.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.805
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.553
Then the running Tails is installed on USB drive "to_upgrade" 17.452
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.919
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.775
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.122
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.993
Then all tps features from the old Tails version are active 1.234
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.390
And the expected persistent files created with the old Tails version are present in the filesystem 1.008
And all persistent directories from the old Tails version have safe access rights 1.796
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:38.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.297
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.171
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.038
And Tor is ready 13.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.942
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.180
Given I shutdown Tails and wait for the computer to power off 5.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.356
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.530
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.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.166
When the network is plugged 0.023
And Tor is ready 10.497
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.889
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.759
Given I shutdown Tails and wait for the computer to power off 2.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.745
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.645
And the file system changes introduced in version 6.3~testoverlayfs are present 0.285
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.035
And Tor is ready 10.314
Then the Upgrader considers the system as up-to-date 0.090
# 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.005
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.065
Tags: @product @automatic_upgrade
19.774
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.035
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.201
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.000