Project Number Date
test_Tails_ISO_web-release-7.12 2 02 Sep 2026, 18:18

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:18.021 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:15.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.677
When I start Tails from USB drive "old" with network unplugged 58.163
Then the boot device has safe access rights 2.330
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 1.298
After features/support/hooks.rb:108 0.008
Tags: @product
1:30.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login 51.687
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 25.831
And I take note of which tps features are available 8.285
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 3.946
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.006
Tags: @product
1:52.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.030
Then Tails is running from USB drive "old" 0.247
And all tps features are active 9.831
When I write some files expected to persist 1.446
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.766
And I take note of which tps features are available 7.859
And I shutdown Tails and wait for the computer to power off 3.967
# 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.772
After features/support/hooks.rb:339 0.251
After features/support/hooks.rb:108 0.010
Tags: @product
2:21.737
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.686
And I log in to a new session 13.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.868
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.590
Then the running Tails is installed on USB drive "to_upgrade" 20.335
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 2.140
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.670
Then all tps features from the old Tails version are active 1.421
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.420
And the expected persistent files created with the old Tails version are present in the filesystem 1.198
And all persistent directories from the old Tails version have safe access rights 1.900
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:40.893
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.288
And no SquashFS delta is installed 0.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.534
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.450
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.027
And Tor is ready 12.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.703
Given I shutdown Tails and wait for the computer to power off 5.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.785
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.491
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.213
When the network is plugged 0.025
And Tor is ready 10.620
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.994
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.819
Given I shutdown Tails and wait for the computer to power off 3.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.437
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.029
And Tor is ready 10.823
Then the Upgrader considers the system as up-to-date 0.095
# 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.491
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
21.045
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.399
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.059
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.511
After features/support/hooks.rb:339 0.697
After features/support/hooks.rb:108 0.000