Project Number Date
test_Tails_ISO_stable 5916 29 Oct 2025, 08:41

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 16:57.601 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
2:21.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 32.189
When I start Tails from USB drive "old" with network unplugged 1:43.465
Then the boot device has safe access rights 3.981
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 4.237
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:30.982
Then Tails is running from USB drive "old" 0.525
And I create a persistent partition 30.839
And I take note of which tps features are available 1.198
Then a Tails persistence partition exists on USB drive "old" 0.676
And I shutdown Tails and wait for the computer to power off 7.671
After features/support/hooks.rb:331 0.774
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.360
Then Tails is running from USB drive "old" 0.695
And all tps features are active 1.978
When I write some files expected to persist 1.810
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.309
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 3.163
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.440
After features/support/hooks.rb:331 0.405
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.545
And I log in to a new session 18.464
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.756
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.073
Then the running Tails is installed on USB drive "to_upgrade" 22.276
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 4.109
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.572
Then all tps features from the old Tails version are active 1.987
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.538
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.245
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
5:12.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.482
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.055
And Tor is ready 14.397
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.820
Given I shutdown Tails and wait for the computer to power off 11.887
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.759
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.759
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.259
When the network is plugged 0.064
And Tor is ready 12.865
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.020
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.204
Given I shutdown Tails and wait for the computer to power off 7.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.174
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.868
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.183
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.300
And Tor is ready 11.857
Then the Upgrader considers the system as up-to-date 0.208
# 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 6.652
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.573
After features/support/hooks.rb:331 1.239
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
24.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 12.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.560
After features/support/hooks.rb:331 0.978
After features/support/hooks.rb:100 0.000