Project Number Date
test_Tails_ISO_stable 5941 10 Nov 2025, 16:49

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:55.736 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:3.883
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.112
When I start Tails from USB drive "old" with network unplugged 1:27.472
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 4.236
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.381
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:25.606
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 29.718
And I take note of which tps features are available 1.222
Then a Tails persistence partition exists on USB drive "old" 0.713
And I shutdown Tails and wait for the computer to power off 7.607
After features/support/hooks.rb:331 0.592
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.596
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.781
When I write some files expected to persist 1.414
# 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.359
And all persistent directories from the old Tails version have safe access rights 2.373
And I take note of which tps features are available 2.525
And I shutdown Tails and wait for the computer to power off 8.611
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.882
After features/support/hooks.rb:331 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.280
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.183
And I log in to a new session 16.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.323
And I plug USB drive "to_upgrade" 2.351
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.084
Then the running Tails is installed on USB drive "to_upgrade" 20.043
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:331 3.713
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.405
Then all tps features from the old Tails version are active 1.576
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.083
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:51.066
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 13.046
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.072
And Tor is ready 13.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.838
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.846
Given I shutdown Tails and wait for the computer to power off 8.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.463
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.878
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.239
When the network is plugged 0.082
And Tor is ready 12.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.802
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.849
Given I shutdown Tails and wait for the computer to power off 4.724
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.783
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.287
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.061
And Tor is ready 11.530
Then the Upgrader considers the system as up-to-date 0.188
# 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.892
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.527
After features/support/hooks.rb:331 1.283
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
25.487
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.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.753
After features/support/hooks.rb:331 0.847
After features/support/hooks.rb:100 0.000