Project Number Date
test_Tails_ISO_stable 6633 03 Sep 2026, 15: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:24.382 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
58.498
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.074
When I start Tails from USB drive "old" with network unplugged 40.469
Then the boot device has safe access rights 2.110
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.636
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 49.714
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 23.806
And I take note of which tps features are available 6.779
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 2.588
After features/support/hooks.rb:339 0.507
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.591
Then Tails is running from USB drive "old" 0.217
And all tps features are active 7.976
When I write some files expected to persist 1.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.572
And I take note of which tps features are available 6.156
And I shutdown Tails and wait for the computer to power off 2.640
# 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.083
After features/support/hooks.rb:339 0.209
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.888
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.922
And I log in to a new session 12.277
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.589
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.204
Then the running Tails is installed on USB drive "to_upgrade" 18.387
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.744
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.579
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.085
And the expected persistent files created with the old Tails version are present in the filesystem 0.873
And all persistent directories from the old Tails version have safe access rights 1.591
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
3:41.214
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.579
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.027
And Tor is ready 11.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.688
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.854
Given I shutdown Tails and wait for the computer to power off 5.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.442
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.514
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.186
When the network is plugged 0.031
And Tor is ready 10.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.993
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.984
Given I shutdown Tails and wait for the computer to power off 4.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.245
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.784
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.030
And Tor is ready 10.599
Then the Upgrader considers the system as up-to-date 0.088
# 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.549
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:339 0.718
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
21.372
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.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 10.355
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.901
After features/support/hooks.rb:339 0.851
After features/support/hooks.rb:108 0.000