Project Number Date
test_Tails_ISO_stable 6283 09 Apr 2026, 12:20

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.292 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.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.319
When I start Tails from USB drive "old" with network unplugged 44.211
Then the boot device has safe access rights 3.024
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 3.635
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.522
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 57.117
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 26.311
And I take note of which tps features are available 0.796
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 7.402
After features/support/hooks.rb:331 0.402
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.994
Then Tails is running from USB drive "old" 0.279
And all tps features are active 1.280
When I write some files expected to persist 1.425
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.561
And all persistent directories from the old Tails version have safe access rights 2.287
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 4.488
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.431
After features/support/hooks.rb:331 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.313
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 8.455
And I log in to a new session 12.724
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.878
And I plug USB drive "to_upgrade" 2.290
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.159
Then the running Tails is installed on USB drive "to_upgrade" 17.521
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.103
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.832
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:8.264
Then all tps features from the old Tails version are active 1.201
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 3.362
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
4:55.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.267
And no SquashFS delta is installed 0.095
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.152
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.017
And Tor is ready 22.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.496
Given I shutdown Tails and wait for the computer to power off 20.955
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.247
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.212
When the network is plugged 0.016
And Tor is ready 23.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.765
Given I shutdown Tails and wait for the computer to power off 17.667
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.784
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.260
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.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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.018
And Tor is ready 21.961
Then the Upgrader considers the system as up-to-date 0.145
# 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.894
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.061
Tags: @product @automatic_upgrade
27.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.854
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.018
And Tor is ready 18.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.427
After features/support/hooks.rb:331 1.048
After features/support/hooks.rb:100 0.000