Project Number Date
test_Tails_ISO_stable 6451 16 Jun 2026, 19:31

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:27.719 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:5.547
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.141
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.143
When I start Tails from USB drive "old" with network unplugged 46.373
Then the boot device has safe access rights 3.133
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.626
After features/support/hooks.rb:108 0.020
Tags: @product
1:35.863
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 56.802
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 26.083
And I take note of which tps features are available 4.845
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 7.019
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.016
Tags: @product
1:44.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.879
Then Tails is running from USB drive "old" 0.290
And all tps features are active 5.413
When I write some files expected to persist 1.456
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 5.016
And I shutdown Tails and wait for the computer to power off 4.411
# 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" 13.121
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.040
Tags: @product
2:14.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.588
And I log in to a new session 13.779
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.916
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.259
Then the running Tails is installed on USB drive "to_upgrade" 16.486
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.349
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.965
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.348
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.540
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.208
After features/support/hooks.rb:339 0.902
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:6.663
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.459
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
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.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.020
And Tor is ready 13.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.257
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.600
Given I shutdown Tails and wait for the computer to power off 10.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.424
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.211
When the network is plugged 0.015
And Tor is ready 11.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.851
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.155
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.702
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.328
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.193
# 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.220
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.014
And Tor is ready 11.596
Then the Upgrader considers the system as up-to-date 10.676
# 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 5.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.499
After features/support/hooks.rb:339 0.798
After features/support/hooks.rb:108 0.058
Tags: @product @automatic_upgrade
21.481
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
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.013
And Tor is ready 10.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.024
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.000