Project Number Date
test_Tails_ISO_stable 6732 09 Oct 2026, 07:28

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:28.673 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:0.519
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.370
When I start Tails from USB drive "old" with network unplugged 43.408
Then the boot device has safe access rights 2.038
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.101
After features/support/hooks.rb:339 3.536
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.264
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 47.479
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 22.612
And I take note of which tps features are available 6.696
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 2.564
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.830
Then Tails is running from USB drive "old" 0.181
And all tps features are active 7.204
When I write some files expected to persist 1.163
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.532
And I take note of which tps features are available 6.557
And I shutdown Tails and wait for the computer to power off 4.063
# 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" 11.738
After features/support/hooks.rb:339 0.496
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.867
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.438
And I log in to a new session 12.461
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.198
Then the running Tails is installed on USB drive "to_upgrade" 18.227
And I unplug USB drive "to_upgrade" 1.375
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:339 1.956
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.797
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.700
Then all tps features from the old Tails version are active 2.394
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 2.179
And the expected persistent files created with the old Tails version are present in the filesystem 1.028
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:46.724
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.697
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.034
And Tor is ready 13.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.145
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.142
Given I shutdown Tails and wait for the computer to power off 5.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.242
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.595
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.195
When the network is plugged 0.030
And Tor is ready 10.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.572
Given I shutdown Tails and wait for the computer to power off 4.108
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.459
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.738
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.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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.027
And Tor is ready 10.367
Then the Upgrader considers the system as up-to-date 10.441
# 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.040
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.657
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 8.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.024
And Tor is ready 10.020
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.116
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.000