Project Number Date
test_Tails_ISO_stable 6471 25 Jun 2026, 11:30

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:32.190 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:1.267
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.045
When I start Tails from USB drive "old" with network unplugged 44.012
Then the boot device has safe access rights 2.473
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.666
After features/support/hooks.rb:108 0.008
Tags: @product
1:29.688
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.465
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 23.541
And I take note of which tps features are available 3.841
Then a Tails persistence partition exists on USB drive "old" 0.491
And I shutdown Tails and wait for the computer to power off 8.016
After features/support/hooks.rb:339 0.186
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.689
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.051
Then Tails is running from USB drive "old" 0.267
And all tps features are active 4.762
When I write some files expected to persist 1.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.791
And I take note of which tps features are available 3.502
And I shutdown Tails and wait for the computer to power off 7.918
# 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.635
After features/support/hooks.rb:339 0.142
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.091
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 without a persistent partition and stopped at Tails Greeter's login screen 7.819
And I log in to a new session 11.445
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.726
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.979
Then the running Tails is installed on USB drive "to_upgrade" 14.623
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 3.576
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.137
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.706
Then all tps features from the old Tails version are active 0.893
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.359
And the expected persistent files created with the old Tails version are present in the filesystem 1.078
And all persistent directories from the old Tails version have safe access rights 1.800
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:48.116
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.064
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.015
And Tor is ready 11.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.130
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.411
Given I shutdown Tails and wait for the computer to power off 10.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.948
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.741
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.194
When the network is plugged 0.015
And Tor is ready 10.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.423
Given I shutdown Tails and wait for the computer to power off 7.967
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.354
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.894
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.016
And Tor is ready 10.100
Then the Upgrader considers the system as up-to-date 10.522
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.774
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
20.200
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.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.433
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.000