Project Number Date
test_Tails_ISO_stable 6000 10 Dec 2025, 22:15

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:53.269 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:55.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 31.309
When I start Tails from USB drive "old" with network unplugged 1:17.572
Then the boot device has safe access rights 3.867
And Tails is running from USB drive "old" 0.828
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 3.993
After features/support/hooks.rb:100 0.012
Tags: @product
2:11.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:29.108
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 32.404
And I take note of which tps features are available 1.305
Then a Tails persistence partition exists on USB drive "old" 0.686
And I shutdown Tails and wait for the computer to power off 7.727
After features/support/hooks.rb:331 0.411
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.142
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.973
When I write some files expected to persist 2.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.601
And I take note of which tps features are available 0.571
And I shutdown Tails and wait for the computer to power off 7.943
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.048
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.501
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 without a persistent partition and stopped at Tails Greeter's login screen 13.303
And I log in to a new session 16.730
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 3.031
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.022
Then the running Tails is installed on USB drive "to_upgrade" 21.540
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 4.299
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.255
Then all tps features from the old Tails version are active 1.871
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.247
And the expected persistent files created with the old Tails version are present in the filesystem 1.658
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:331 1.285
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
4:42.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.705
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.057
And Tor is ready 14.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.562
Given I shutdown Tails and wait for the computer to power off 11.955
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.206
Then Tails is running version 6.2~testoverlayfs 0.250
And all tps features are active 3.565
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.216
# 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.262
When the network is plugged 0.105
And Tor is ready 12.719
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.904
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.849
Given I shutdown Tails and wait for the computer to power off 8.255
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.327
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.845
And the file system changes introduced in version 6.3~testoverlayfs are present 0.641
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.212
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.068
And Tor is ready 12.203
Then the Upgrader considers the system as up-to-date 0.116
# 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 7.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.596
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
27.901
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 11.718
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 13.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.929
After features/support/hooks.rb:331 1.016
After features/support/hooks.rb:100 0.000