Project Number Date
test_Tails_ISO_devel 4154 06 Jan 2026, 12:47

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 14:16.133 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:40.118
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 30.929
When I start Tails from USB drive "old" with network unplugged 1:3.813
Then the boot device has safe access rights 3.191
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:331 3.614
After features/support/hooks.rb:100 0.009
Tags: @product
1:37.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:1.273
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 28.765
And I take note of which tps features are available 1.253
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 4.846
After features/support/hooks.rb:331 0.665
After features/support/hooks.rb:100 0.008
Tags: @product
1:47.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.654
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.915
When I write some files expected to persist 1.642
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.155
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 7.537
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.794
After features/support/hooks.rb:331 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.394
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 without a persistent partition and stopped at Tails Greeter's login screen 12.658
And I log in to a new session 22.539
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.340
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.934
Then the running Tails is installed on USB drive "to_upgrade" 20.066
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 3.693
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:32.073
Then all tps features from the old Tails version are active 1.416
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.947
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 1.976
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:12.198
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.868
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.055
And Tor is ready 13.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.828
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.417
Given I shutdown Tails and wait for the computer to power off 11.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.878
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.874
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.244
When the network is plugged 0.073
And Tor is ready 12.313
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.576
Given I shutdown Tails and wait for the computer to power off 7.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.337
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.055
And Tor is ready 11.224
Then the Upgrader considers the system as up-to-date 0.131
# 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.331
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.548
After features/support/hooks.rb:331 1.209
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.663
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.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.216
And the signing key used by the Upgrader is outdated 0.268
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 11.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.625
After features/support/hooks.rb:331 0.665
After features/support/hooks.rb:100 0.000