Project Number Date
test_Tails_ISO_devel 4632 21 Sep 2026, 18:46

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 11:35.755 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:11.833
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.397
When I start Tails from USB drive "old" with network unplugged 54.539
Then the boot device has safe access rights 2.138
And Tails is running from USB drive "old" 0.163
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 1.984
After features/support/hooks.rb:108 0.009
Tags: @product
1:21.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.675
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.073
And I take note of which tps features are available 5.933
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 3.901
After features/support/hooks.rb:339 0.437
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.425
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.858
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.341
When I write some files expected to persist 1.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.618
And I take note of which tps features are available 6.466
And I shutdown Tails and wait for the computer to power off 2.632
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.715
After features/support/hooks.rb:339 0.374
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.390
And I log in to a new session 12.081
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.801
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.517
Then the running Tails is installed on USB drive "to_upgrade" 18.159
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.598
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.246
Then all tps features from the old Tails version are active 0.923
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 1.842
And the expected persistent files created with the old Tails version are present in the filesystem 0.820
And all persistent directories from the old Tails version have safe access rights 1.542
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:52.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.052
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.031
And Tor is ready 12.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.140
Given I shutdown Tails and wait for the computer to power off 5.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.887
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.700
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.077
# 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.196
When the network is plugged 0.031
And Tor is ready 10.085
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.652
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.158
Given I shutdown Tails and wait for the computer to power off 4.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.646
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.816
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.031
And Tor is ready 10.346
Then the Upgrader considers the system as up-to-date 10.395
# 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 3.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.359
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.032
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.086
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.071
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.000