Project Number Date
test_Tails_ISO_stable 6265 05 Apr 2026, 11:29

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 13:52.545 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:32.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.428
When I start Tails from USB drive "old" with network unplugged 1:11.823
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.590
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 56.784
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 25.855
And I take note of which tps features are available 0.871
Then a Tails persistence partition exists on USB drive "old" 0.596
And I shutdown Tails and wait for the computer to power off 4.254
After features/support/hooks.rb:331 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.631
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.142
When I write some files expected to persist 1.310
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.652
And all persistent directories from the old Tails version have safe access rights 2.307
And I take note of which tps features are available 0.176
And I shutdown Tails and wait for the computer to power off 8.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.251
After features/support/hooks.rb:331 0.472
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.289
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.825
And I log in to a new session 18.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.880
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.038
Then the running Tails is installed on USB drive "to_upgrade" 17.659
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:331 4.009
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.436
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.547
Then all tps features from the old Tails version are active 1.238
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 3.044
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.009
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.006
5:9.239
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.599
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.017
And Tor is ready 44.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.301
Given I shutdown Tails and wait for the computer to power off 16.782
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.533
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.319
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.297
When the network is plugged 0.018
And Tor is ready 20.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.780
Given I shutdown Tails and wait for the computer to power off 17.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.560
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.241
And the file system changes introduced in version 6.3~testoverlayfs are present 0.430
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.014
And Tor is ready 21.113
Then the Upgrader considers the system as up-to-date 0.086
# 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.627
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:331 0.845
After features/support/hooks.rb:100 0.011
30.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.367
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 20.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
After features/support/hooks.rb:331 1.180
After features/support/hooks.rb:100 0.000