Project Number Date
test_Tails_ISO_21575-dirtyfrag 1 08 May 2026, 13:56

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:25.046 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:3.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.410
When I start Tails from USB drive "old" with network unplugged 45.734
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 1.456
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.457
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 24.401
And I take note of which tps features are available 0.693
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 5.496
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.886
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.334
When I write some files expected to persist 1.397
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 4.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.125
After features/support/hooks.rb:331 0.557
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.074
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 without a persistent partition and stopped at Tails Greeter's login screen 7.484
And I log in to a new session 13.692
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.816
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.881
Then the running Tails is installed on USB drive "to_upgrade" 16.663
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 2.117
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.025
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.752
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 1.852
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:37.976
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 with a persistent partition enabled and logged in 8.388
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.021
And Tor is ready 21.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.659
Given I shutdown Tails and wait for the computer to power off 20.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.558
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.310
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.262
When the network is plugged 0.033
And Tor is ready 21.494
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.799
Given I shutdown Tails and wait for the computer to power off 13.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.755
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.166
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.015
And Tor is ready 20.895
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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:331 1.005
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.454
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.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 17.333
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
After features/support/hooks.rb:331 0.756
After features/support/hooks.rb:100 0.000