Project Number Date
test_Tails_ISO_stable 6620 01 Sep 2026, 15: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:10.038 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:6.961
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.969
When I start Tails from USB drive "old" with network unplugged 50.518
Then the boot device has safe access rights 1.830
And Tails is running from USB drive "old" 0.172
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.130
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.688
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.449
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 45.702
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 22.816
And I take note of which tps features are available 6.146
Then a Tails persistence partition exists on USB drive "old" 0.493
And I shutdown Tails and wait for the computer to power off 4.015
After features/support/hooks.rb:339 0.399
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.936
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.377
Then Tails is running from USB drive "old" 0.195
And all tps features are active 6.928
When I write some files expected to persist 0.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.223
And all persistent directories from the old Tails version have safe access rights 1.443
And I take note of which tps features are available 6.037
And I shutdown Tails and wait for the computer to power off 2.697
# 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" 10.879
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.089
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.999
And I log in to a new session 9.916
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.550
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.321
Then the running Tails is installed on USB drive "to_upgrade" 17.832
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.448
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.475
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.759
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.062
And the expected persistent files created with the old Tails version are present in the filesystem 0.980
And all persistent directories from the old Tails version have safe access rights 1.370
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:43.391
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.197
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.141
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.031
And Tor is ready 11.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.656
Given I shutdown Tails and wait for the computer to power off 5.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.936
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.447
And the file system changes introduced in version 6.2~testoverlayfs are present 0.160
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.076
# 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.153
When the network is plugged 0.036
And Tor is ready 10.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.850
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.557
Given I shutdown Tails and wait for the computer to power off 2.587
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.165
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.921
And the file system changes introduced in version 6.3~testoverlayfs are present 0.279
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.034
And Tor is ready 10.107
Then the Upgrader considers the system as up-to-date 10.416
# 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.005
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
17.735
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.650
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
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.033
And Tor is ready 7.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.845
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.000