Project Number Date
test_Tails_ISO_stable 6612 28 Aug 2026, 07:22

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:33.113 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.305
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 13.490
When I start Tails from USB drive "old" with network unplugged 54.841
Then the boot device has safe access rights 2.101
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:339 3.749
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.138
And I start Tails from USB drive "old" with network unplugged and I login 49.490
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 22.873
And I take note of which tps features are available 6.515
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 5.302
After features/support/hooks.rb:339 0.332
After features/support/hooks.rb:108 0.009
Tags: @product
1:33.021
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.466
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.887
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 1.737
And I take note of which tps features are available 6.097
And I shutdown Tails and wait for the computer to power off 2.509
# 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.206
After features/support/hooks.rb:339 0.248
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.175
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.328
And I log in to a new session 12.594
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.672
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.394
Then the running Tails is installed on USB drive "to_upgrade" 17.638
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:339 1.712
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.897
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.346
Then all tps features from the old Tails version are active 1.311
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.377
And the expected persistent files created with the old Tails version are present in the filesystem 0.868
And all persistent directories from the old Tails version have safe access rights 1.669
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:41.466
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.139
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.190
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.027
And Tor is ready 13.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.992
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 5.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.834
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.651
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.093
# 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.169
When the network is plugged 0.039
And Tor is ready 10.366
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.755
Given I shutdown Tails and wait for the computer to power off 2.635
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.150
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.076
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.027
And Tor is ready 9.988
Then the Upgrader considers the system as up-to-date 10.479
# 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 3.517
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.131
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.699
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.032
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.609
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.000