Project Number Date
test_Tails_ISO_devel 4079 19 Nov 2025, 13:12

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:33.821 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.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.267
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.353
When I start Tails from USB drive "old" with network unplugged 1:10.455
Then the boot device has safe access rights 3.116
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:331 3.630
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.342
And I start Tails from USB drive "old" with network unplugged and I login 1:26.366
Then Tails is running from USB drive "old" 0.471
And I create a persistent partition 29.567
And I take note of which tps features are available 1.232
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.763
After features/support/hooks.rb:331 0.606
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.093
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.545
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.216
When I write some files expected to persist 1.872
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 2.572
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 7.681
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.422
After features/support/hooks.rb:331 0.319
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.040
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 11.063
And I log in to a new session 17.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.858
And I plug USB drive "to_upgrade" 2.690
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.777
Then the running Tails is installed on USB drive "to_upgrade" 25.888
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:331 3.998
After features/support/hooks.rb:100 0.000
Tags: @product
1:57.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.156
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:44.326
Then all tps features from the old Tails version are active 5.972
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.359
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 2.375
After features/support/hooks.rb:331 0.997
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:10.519
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 21.226
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.338
And Tor is ready 17.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.095
Given I shutdown Tails and wait for the computer to power off 10.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.806
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.926
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.224
When the network is plugged 0.059
And Tor is ready 12.584
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.373
Given I shutdown Tails and wait for the computer to power off 7.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.487
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.052
And Tor is ready 11.914
Then the Upgrader considers the system as up-to-date 0.225
# 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.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.741
After features/support/hooks.rb:331 1.335
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
24.594
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 11.880
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 10.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.823
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.000