Project Number Date
test_Tails_ISO_devel 4056 05 Nov 2025, 19:42

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:9.411 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.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.168
When I start Tails from USB drive "old" with network unplugged 1:11.571
Then the boot device has safe access rights 2.859
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 3.552
After features/support/hooks.rb:100 0.011
Tags: @product
2:1.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:24.886
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 27.025
And I take note of which tps features are available 1.039
Then a Tails persistence partition exists on USB drive "old" 0.681
And I shutdown Tails and wait for the computer to power off 7.532
After features/support/hooks.rb:331 0.261
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.423
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.143
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.841
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.596
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 7.786
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.904
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.098
And I log in to a new session 16.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.733
And I plug USB drive "to_upgrade" 2.544
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.668
Then the running Tails is installed on USB drive "to_upgrade" 19.983
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 4.153
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.671
Then all tps features from the old Tails version are active 1.636
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.103
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.064
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:24.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.472
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
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.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.062
And Tor is ready 13.591
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.871
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.815
Given I shutdown Tails and wait for the computer to power off 11.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.239
Then Tails is running version 6.2~testoverlayfs 0.112
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.402
When the network is plugged 0.055
And Tor is ready 10.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.677
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.603
Given I shutdown Tails and wait for the computer to power off 7.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.155
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.322
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.052
And Tor is ready 42.737
Then the Upgrader considers the system as up-to-date 0.202
# 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.222
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.478
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
26.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
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.064
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.790
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.866
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.000