Project Number Date
test_Tails_ISO_stable 6463 18 Jun 2026, 16:21

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:47.091 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.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.794
When I start Tails from USB drive "old" with network unplugged 42.231
Then the boot device has safe access rights 2.576
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.533
After features/support/hooks.rb:108 0.022
Tags: @product
1:30.484
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login 52.770
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 24.601
And I take note of which tps features are available 3.776
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 8.449
After features/support/hooks.rb:339 0.386
After features/support/hooks.rb:108 0.022
Tags: @product
1:35.923
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.141
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.544
Then Tails is running from USB drive "old" 0.245
And all tps features are active 4.873
When I write some files expected to persist 1.290
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.007
And I take note of which tps features are available 4.009
And I shutdown Tails and wait for the computer to power off 7.013
# 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.239
After features/support/hooks.rb:339 0.442
After features/support/hooks.rb:108 0.023
Tags: @product
2:10.469
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 8.349
And I log in to a new session 11.666
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.846
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.366
Then the running Tails is installed on USB drive "to_upgrade" 15.775
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 3.915
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.177
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.147
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.718
Then all tps features from the old Tails version are active 1.081
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.143
And all persistent directories from the old Tails version have safe access rights 2.121
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:55.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.500
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.017
And Tor is ready 13.179
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.742
Given I shutdown Tails and wait for the computer to power off 10.117
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.533
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.927
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.220
When the network is plugged 0.014
And Tor is ready 9.641
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.859
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.259
Given I shutdown Tails and wait for the computer to power off 7.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.516
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.019
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.040
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.015
And Tor is ready 11.015
Then the Upgrader considers the system as up-to-date 10.548
# 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.335
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.999
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
20.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.047
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.921
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.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.711
After features/support/hooks.rb:339 0.707
After features/support/hooks.rb:108 0.000