Project Number Date
test_Tails_ISO_devel 4162 13 Jan 2026, 16:27

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 14:26.916 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:36.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 39.299
When I start Tails from USB drive "old" with network unplugged 52.294
Then the boot device has safe access rights 3.243
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 4.121
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.294
And I start Tails from USB drive "old" with network unplugged and I login 1:4.724
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 28.892
And I take note of which tps features are available 1.126
Then a Tails persistence partition exists on USB drive "old" 0.710
And I shutdown Tails and wait for the computer to power off 7.686
After features/support/hooks.rb:331 0.270
After features/support/hooks.rb:100 0.009
Tags: @product
1:50.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.836
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.948
When I write some files expected to persist 2.156
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
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.197
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 7.676
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.323
After features/support/hooks.rb:331 0.235
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.214
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 13.107
And I log in to a new session 13.286
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.455
And I plug USB drive "to_upgrade" 1.926
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.899
Then the running Tails is installed on USB drive "to_upgrade" 19.142
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 4.317
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.239
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.145
Then all tps features from the old Tails version are active 1.906
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 2.986
And the expected persistent files created with the old Tails version are present in the filesystem 1.211
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:29.280
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 13.457
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.052
And Tor is ready 13.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.790
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.392
Given I shutdown Tails and wait for the computer to power off 11.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.655
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 3.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.250
When the network is plugged 0.082
And Tor is ready 12.965
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.557
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.408
Given I shutdown Tails and wait for the computer to power off 7.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.119
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.597
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
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.210
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.092
And Tor is ready 12.453
Then the Upgrader considers the system as up-to-date 0.145
# 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.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.531
After features/support/hooks.rb:331 0.892
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
25.895
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 12.332
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 1.414
And Tor is ready 11.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.584
After features/support/hooks.rb:331 1.145
After features/support/hooks.rb:100 0.000