Project Number Date
test_Tails_ISO_stable 5978 01 Dec 2025, 16:24

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:22.037 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:59.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 28.231
When I start Tails from USB drive "old" with network unplugged 1:25.891
Then the boot device has safe access rights 2.932
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 3.576
After features/support/hooks.rb:100 0.009
Tags: @product
1:56.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:23.909
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 27.459
And I take note of which tps features are available 1.132
Then a Tails persistence partition exists on USB drive "old" 0.640
And I shutdown Tails and wait for the computer to power off 3.241
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.575
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.072
When I write some files expected to persist 1.827
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.351
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.847
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.425
After features/support/hooks.rb:331 0.562
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.177
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 9.945
And I log in to a new session 11.598
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.649
And I plug USB drive "to_upgrade" 3.948
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.885
Then the running Tails is installed on USB drive "to_upgrade" 20.790
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:331 3.576
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.270
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.117
Then all tps features from the old Tails version are active 1.931
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 4.042
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.981
After features/support/hooks.rb:331 0.727
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
5:38.737
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 10.259
And no SquashFS delta is installed 0.082
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.059
And Tor is ready 42.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.244
Given I shutdown Tails and wait for the computer to power off 8.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.413
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.528
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.191
# 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.488
When the network is plugged 0.071
And Tor is ready 12.640
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.910
Given I shutdown Tails and wait for the computer to power off 8.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.633
Then Tails is running version 6.3~testoverlayfs 0.133
And all tps features are active 3.391
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.356
And Tor is ready 12.463
Then the Upgrader considers the system as up-to-date 0.219
# 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.867
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.599
After features/support/hooks.rb:331 1.084
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
21.776
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 with a persistent partition enabled and logged in 9.866
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.086
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 9.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.697
After features/support/hooks.rb:331 1.176
After features/support/hooks.rb:100 0.000