Project Number Date
test_Tails_ISO_stable 6540 28 Jul 2026, 19:58

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:57.754 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:12.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.719
When I start Tails from USB drive "old" with network unplugged 53.690
Then the boot device has safe access rights 2.916
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.444
After features/support/hooks.rb:108 0.015
Tags: @product
1:28.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.024
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 24.493
And I take note of which tps features are available 3.728
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.057
After features/support/hooks.rb:339 0.255
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.794
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.450
Then Tails is running from USB drive "old" 0.252
And all tps features are active 4.917
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 1.865
And I take note of which tps features are available 4.094
And I shutdown Tails and wait for the computer to power off 4.211
# 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.130
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.319
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 7.753
And I log in to a new session 11.092
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.957
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.227
Then the running Tails is installed on USB drive "to_upgrade" 15.710
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 2.216
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.888
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.347
Then all tps features from the old Tails version are active 1.066
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.647
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:55.816
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.309
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.296
When the network is plugged 0.017
And Tor is ready 13.046
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.451
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.002
Given I shutdown Tails and wait for the computer to power off 6.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.727
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.625
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.196
When the network is plugged 0.019
And Tor is ready 11.673
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.802
Given I shutdown Tails and wait for the computer to power off 4.094
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.073
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.013
And Tor is ready 10.306
Then the Upgrader considers the system as up-to-date 10.544
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 1.038
After features/support/hooks.rb:108 0.085
Tags: @product @automatic_upgrade
21.628
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.621
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.009
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.610
After features/support/hooks.rb:339 0.606
After features/support/hooks.rb:108 0.000