Project Number Date
test_Tails_ISO_devel 4097 02 Dec 2025, 12:51

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 15:43.481 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:51.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.512
When I start Tails from USB drive "old" with network unplugged 1:14.180
Then the boot device has safe access rights 4.068
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:331 3.726
After features/support/hooks.rb:100 0.018
Tags: @product
2:12.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:27.545
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 33.260
And I take note of which tps features are available 1.273
Then a Tails persistence partition exists on USB drive "old" 0.630
And I shutdown Tails and wait for the computer to power off 9.262
After features/support/hooks.rb:331 0.616
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.502
Then Tails is running from USB drive "old" 0.789
And all tps features are active 2.197
When I write some files expected to persist 1.658
# 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.355
And all persistent directories from the old Tails version have safe access rights 2.436
And I take note of which tps features are available 0.513
And I shutdown Tails and wait for the computer to power off 7.549
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.069
After features/support/hooks.rb:331 0.455
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.280
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 11.354
And I log in to a new session 13.820
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.238
And I plug USB drive "to_upgrade" 3.039
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.626
Then the running Tails is installed on USB drive "to_upgrade" 20.816
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 3.604
After features/support/hooks.rb:100 0.000
Tags: @product
1:35.548
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:25.352
Then all tps features from the old Tails version are active 2.433
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.305
And all persistent directories from the old Tails version have safe access rights 2.582
After features/support/hooks.rb:331 0.928
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:52.689
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 11.165
And no SquashFS delta is installed 0.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.627
When the network is plugged 0.063
And Tor is ready 42.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.386
Given I shutdown Tails and wait for the computer to power off 9.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.047
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.512
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
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.146
# 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.261
When the network is plugged 0.059
And Tor is ready 12.820
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.623
Given I shutdown Tails and wait for the computer to power off 8.057
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.273
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 2.847
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.209
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.466
When the network is plugged 0.054
And Tor is ready 11.018
Then the Upgrader considers the system as up-to-date 0.237
# 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 7.595
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.679
After features/support/hooks.rb:331 1.150
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.884
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 10.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.851
After features/support/hooks.rb:331 1.110
After features/support/hooks.rb:100 0.000