Project Number Date
test_Tails_ISO_devel 4103 06 Dec 2025, 12:49

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 17:34.730 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:27.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 55.895
When I start Tails from USB drive "old" with network unplugged 1:25.296
Then the boot device has safe access rights 3.799
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:331 3.924
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.217
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:29.822
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 44.620
And I take note of which tps features are available 1.376
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.082
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.670
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.842
Then Tails is running from USB drive "old" 0.806
And all tps features are active 2.243
When I write some files expected to persist 1.860
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.490
And I take note of which tps features are available 0.817
And I shutdown Tails and wait for the computer to power off 8.833
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.991
After features/support/hooks.rb:331 0.397
After features/support/hooks.rb:100 0.009
Tags: @product
3:12.768
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 without a persistent partition and stopped at Tails Greeter's login screen 21.971
And I log in to a new session 18.446
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.217
And I plug USB drive "to_upgrade" 2.725
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.616
Then the running Tails is installed on USB drive "to_upgrade" 20.322
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:331 4.197
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.143
Given a computer 0.474
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.548
Then all tps features from the old Tails version are active 2.118
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.406
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.294
After features/support/hooks.rb:331 1.094
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:2.108
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 13.389
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
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.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.059
And Tor is ready 15.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.549
Given I shutdown Tails and wait for the computer to power off 10.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.823
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 3.315
And the file system changes introduced in version 6.2~testoverlayfs are present 0.409
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.227
# 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.274
When the network is plugged 0.273
And Tor is ready 11.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.916
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.332
Given I shutdown Tails and wait for the computer to power off 7.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.731
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 5.688
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.233
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.050
And Tor is ready 42.079
Then the Upgrader considers the system as up-to-date 0.134
# 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 5.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.483
After features/support/hooks.rb:331 1.310
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
28.098
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 12.385
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 13.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.975
After features/support/hooks.rb:331 0.806
After features/support/hooks.rb:100 0.000