Project Number Date
test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring 3 10 Aug 2026, 16:51

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:24.159 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:15.495
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.137
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.169
When I start Tails from USB drive "old" with network unplugged 58.340
Then the boot device has safe access rights 2.220
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 3.712
After features/support/hooks.rb:108 0.020
Tags: @product
1:24.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 48.904
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 23.976
And I take note of which tps features are available 6.627
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 4.076
After features/support/hooks.rb:339 0.495
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.265
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.220
Then Tails is running from USB drive "old" 0.204
And all tps features are active 7.405
When I write some files expected to persist 1.138
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.609
And I take note of which tps features are available 6.508
And I shutdown Tails and wait for the computer to power off 4.136
# 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.491
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.021
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 without a persistent partition and stopped at Tails Greeter's login screen 8.685
And I log in to a new session 11.880
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.107
Then the running Tails is installed on USB drive "to_upgrade" 19.231
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 3.834
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.299
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.414
And the expected persistent files created with the old Tails version are present in the filesystem 0.959
And all persistent directories from the old Tails version have safe access rights 1.762
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:28.125
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 8.049
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.062
And Tor is ready 11.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.083
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.353
Given I shutdown Tails and wait for the computer to power off 5.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.441
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.661
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.193
When the network is plugged 0.038
And Tor is ready 10.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.487
Given I shutdown Tails and wait for the computer to power off 2.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.901
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.025
And Tor is ready 10.106
Then the Upgrader considers the system as up-to-date 0.177
# 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.151
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
18.032
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.789
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.853
After features/support/hooks.rb:339 0.638
After features/support/hooks.rb:108 0.000