Project Number Date
test_Tails_ISO_stable 5926 03 Nov 2025, 08:33

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:56.191 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:0.747
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 25.399
When I start Tails from USB drive "old" with network unplugged 1:30.043
Then the boot device has safe access rights 3.091
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.239
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:331 3.485
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.901
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:25.407
Then Tails is running from USB drive "old" 0.570
And I create a persistent partition 29.135
And I take note of which tps features are available 1.372
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 7.562
After features/support/hooks.rb:331 0.550
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.453
Then Tails is running from USB drive "old" 0.491
And all tps features are active 2.365
When I write some files expected to persist 1.698
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 0.644
And I shutdown Tails and wait for the computer to power off 7.995
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.196
After features/support/hooks.rb:331 0.260
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.691
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 9.676
And I log in to a new session 16.634
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.266
And I plug USB drive "to_upgrade" 2.335
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.681
Then the running Tails is installed on USB drive "to_upgrade" 19.695
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 3.828
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.343
Then all tps features from the old Tails version are active 1.675
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.116
And the expected persistent files created with the old Tails version are present in the filesystem 1.358
And all persistent directories from the old Tails version have safe access rights 2.342
After features/support/hooks.rb:331 0.948
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:57.749
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.543
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.072
And Tor is ready 13.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.442
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.210
Given I shutdown Tails and wait for the computer to power off 10.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.034
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.518
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.231
When the network is plugged 0.071
And Tor is ready 12.637
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.656
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.146
Given I shutdown Tails and wait for the computer to power off 7.854
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.634
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.065
And Tor is ready 12.594
Then the Upgrader considers the system as up-to-date 0.210
# 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.276
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.479
After features/support/hooks.rb:331 0.923
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
23.438
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 9.994
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 11.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.757
After features/support/hooks.rb:331 1.134
After features/support/hooks.rb:100 0.000