Project Number Date
test_Tails_ISO_stable 5949 13 Nov 2025, 08:38

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:25.138 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:13.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.263
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 35.690
When I start Tails from USB drive "old" with network unplugged 1:32.673
Then the boot device has safe access rights 2.602
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 5.055
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 2.727
And I start Tails from USB drive "old" with network unplugged and I login 1:29.262
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 32.879
And I take note of which tps features are available 3.581
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.076
After features/support/hooks.rb:331 0.367
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.603
Then Tails is running from USB drive "old" 0.527
And all tps features are active 2.295
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.527
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 7.647
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.599
After features/support/hooks.rb:331 0.393
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.941
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 13.252
And I log in to a new session 19.060
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.459
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.922
Then the running Tails is installed on USB drive "to_upgrade" 23.381
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 3.744
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.265
Then all tps features from the old Tails version are active 1.910
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.351
And the expected persistent files created with the old Tails version are present in the filesystem 1.399
And all persistent directories from the old Tails version have safe access rights 2.159
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:37.579
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 24.394
And no SquashFS delta is installed 0.685
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 6.764
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.070
And Tor is ready 13.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.645
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.759
Given I shutdown Tails and wait for the computer to power off 11.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.141
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.123
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.230
When the network is plugged 0.065
And Tor is ready 13.180
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.745
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.543
Given I shutdown Tails and wait for the computer to power off 8.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.303
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.765
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.069
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.064
And Tor is ready 12.774
Then the Upgrader considers the system as up-to-date 0.215
# 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 6.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.494
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
25.476
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 11.683
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 11.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.778
After features/support/hooks.rb:331 1.183
After features/support/hooks.rb:100 0.000