Project Number Date
test_Tails_ISO_devel 4050 03 Nov 2025, 13:25

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:52.733 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:47.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.102
When I start Tails from USB drive "old" with network unplugged 1:11.675
Then the boot device has safe access rights 3.813
And Tails is running from USB drive "old" 0.444
And there is no persistence partition on USB drive "old" 0.107
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:331 3.754
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:29.274
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 30.222
And I take note of which tps features are available 1.448
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 7.645
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.980
Then Tails is running from USB drive "old" 0.886
And all tps features are active 2.334
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.593
And I shutdown Tails and wait for the computer to power off 7.987
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.507
After features/support/hooks.rb:331 0.474
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.624
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 13.500
And I log in to a new session 17.256
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.330
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.272
Then the running Tails is installed on USB drive "to_upgrade" 21.474
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:331 3.663
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.726
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.485
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.447
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
5:39.309
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 13.010
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.071
And Tor is ready 14.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.333
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.369
Given I shutdown Tails and wait for the computer to power off 11.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.909
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.408
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.575
When the network is plugged 0.106
And Tor is ready 12.128
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.416
Given I shutdown Tails and wait for the computer to power off 8.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.705
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.722
And the file system changes introduced in version 6.3~testoverlayfs are present 0.702
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.215
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.069
And Tor is ready 12.524
Then the Upgrader considers the system as up-to-date 10.957
# 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.859
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.469
After features/support/hooks.rb:331 1.062
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.811
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.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 11.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.310
After features/support/hooks.rb:331 1.207
After features/support/hooks.rb:100 0.000