Project Number Date
test_Tails_ISO_stable 6016 19 Dec 2025, 11: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 13:30.793 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:48.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.636
When I start Tails from USB drive "old" with network unplugged 1:13.358
Then the boot device has safe access rights 3.107
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 3.801
After features/support/hooks.rb:100 0.016
Tags: @product
1:35.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:1.432
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 28.665
And I take note of which tps features are available 1.011
Then a Tails persistence partition exists on USB drive "old" 0.618
And I shutdown Tails and wait for the computer to power off 3.165
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.010
Tags: @product
1:42.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.482
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.748
When I write some files expected to persist 1.535
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.132
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 7.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.599
After features/support/hooks.rb:331 0.559
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.375
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 12.160
And I log in to a new session 15.360
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.465
And I plug USB drive "to_upgrade" 2.613
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.225
Then the running Tails is installed on USB drive "to_upgrade" 19.165
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:331 4.176
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.036
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.923
Then all tps features from the old Tails version are active 1.276
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.889
And the expected persistent files created with the old Tails version are present in the filesystem 1.228
And all persistent directories from the old Tails version have safe access rights 2.207
After features/support/hooks.rb:331 0.841
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:11.175
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.143
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.058
And Tor is ready 14.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.651
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.303
Given I shutdown Tails and wait for the computer to power off 9.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.941
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.942
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.048
And Tor is ready 12.208
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.558
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.464
Given I shutdown Tails and wait for the computer to power off 7.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.438
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.903
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.050
And Tor is ready 10.422
Then the Upgrader considers the system as up-to-date 10.633
# 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.106
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.322
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 10.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 11.074
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.551
After features/support/hooks.rb:331 1.008
After features/support/hooks.rb:100 0.000