Project Number Date
test_Tails_ISO_stable 6717 01 Oct 2026, 17:45

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:44.358 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:13.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
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 55.597
Then the boot device has safe access rights 2.111
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.837
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.038
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 49.318
Then Tails is running from USB drive "old" 0.181
And I create a persistent partition 24.475
And I take note of which tps features are available 6.591
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 3.852
After features/support/hooks.rb:339 0.270
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.328
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.500
Then Tails is running from USB drive "old" 0.210
And all tps features are active 8.234
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.818
And I take note of which tps features are available 5.855
And I shutdown Tails and wait for the computer to power off 2.607
# 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.342
After features/support/hooks.rb:339 0.500
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.851
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 8.396
And I log in to a new session 12.466
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.702
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.565
Then the running Tails is installed on USB drive "to_upgrade" 18.269
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 1.932
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.139
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.304
Then all tps features from the old Tails version are active 1.142
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.113
And the expected persistent files created with the old Tails version are present in the filesystem 0.940
And all persistent directories from the old Tails version have safe access rights 1.606
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:48.924
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 21.988
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.041
And Tor is ready 13.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.311
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.673
Given I shutdown Tails and wait for the computer to power off 5.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.536
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.166
When the network is plugged 0.022
And Tor is ready 10.606
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.534
Given I shutdown Tails and wait for the computer to power off 2.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.959
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.769
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.028
And Tor is ready 10.529
Then the Upgrader considers the system as up-to-date 0.103
# 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.586
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.988
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
19.523
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.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.171
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.339
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.000