Project Number Date
test_Tails_ISO_tps-restart-gnome-software 4 11 Jun 2026, 16:11

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:4.373 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:8.959
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.405
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.163
And I write an old version of the Tails USB image to disk "old" 14.451
When I start Tails from USB drive "old" with network unplugged 49.717
Then the boot device has safe access rights 2.561
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.210
After features/support/hooks.rb:108 0.004
Tags: @product
1:26.494
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.000
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 50.475
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.367
And I take note of which tps features are available 3.961
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 7.837
After features/support/hooks.rb:339 0.346
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.945
Then Tails is running from USB drive "old" 0.205
And all tps features are active 4.707
When I write some files expected to persist 1.111
# 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.332
And all persistent directories from the old Tails version have safe access rights 1.748
And I take note of which tps features are available 3.512
And I shutdown Tails and wait for the computer to power off 2.598
# 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.495
After features/support/hooks.rb:339 0.404
After features/support/hooks.rb:108 0.005
Tags: @product
3:9.538
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 1:12.718
And I log in to a new session 8.727
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.596
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.032
Then the running Tails is installed on USB drive "to_upgrade" 13.970
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.563
After features/support/hooks.rb:108 0.005
Tags: @product
1:8.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.478
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.902
After features/support/hooks.rb:339 1.032
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
6:26.448
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 2:56.043
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
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.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.018
And Tor is ready 10.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.908
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.075
Given I shutdown Tails and wait for the computer to power off 7.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.818
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.744
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.180
When the network is plugged 0.013
And Tor is ready 10.699
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.553
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.919
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.666
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.014
And Tor is ready 9.670
Then the Upgrader considers the system as up-to-date 10.484
# 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 4.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.802
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.075
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.047
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.257
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.000