Project Number Date
test_Tails_ISO_stable 6427 04 Jun 2026, 07:22

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:5.680 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
57.645
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.549
When I start Tails from USB drive "old" with network unplugged 40.045
Then the boot device has safe access rights 2.253
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:335 3.400
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.149
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 52.894
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 24.202
And I take note of which tps features are available 0.326
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 7.881
After features/support/hooks.rb:335 0.164
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.700
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.257
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.182
When I write some files expected to persist 1.329
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.879
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.183
# 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" 11.896
After features/support/hooks.rb:335 0.192
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.792
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.446
And I log in to a new session 12.690
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.199
Then the running Tails is installed on USB drive "to_upgrade" 15.285
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.297
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.241
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.475
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.479
And the expected persistent files created with the old Tails version are present in the filesystem 1.037
And all persistent directories from the old Tails version have safe access rights 2.000
After features/support/hooks.rb:335 0.574
After features/support/hooks.rb:104 0.006
3:38.907
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.882
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.015
And Tor is ready 11.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.267
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.311
Given I shutdown Tails and wait for the computer to power off 9.462
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.818
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.187
When the network is plugged 0.017
And Tor is ready 11.003
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.589
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.974
Given I shutdown Tails and wait for the computer to power off 7.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.789
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.013
And Tor is ready 11.231
Then the Upgrader considers the system as up-to-date 10.527
# 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.295
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:335 1.035
After features/support/hooks.rb:104 0.010
20.243
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.480
After features/support/hooks.rb:335 0.943
After features/support/hooks.rb:104 0.000