Project Number Date
test_Tails_ISO_21569-fix-gnome-software-notifications 2 02 Oct 2026, 18:32

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:7.944 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:4.126
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.144
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 13.404
When I start Tails from USB drive "old" with network unplugged 46.767
Then the boot device has safe access rights 2.104
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.408
After features/support/hooks.rb:108 0.006
Tags: @product
1:19.652
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 46.642
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 22.661
And I take note of which tps features are available 6.783
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 2.600
After features/support/hooks.rb:339 0.200
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.008
Then Tails is running from USB drive "old" 0.214
And all tps features are active 7.349
When I write some files expected to persist 1.089
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.180
And all persistent directories from the old Tails version have safe access rights 1.652
And I take note of which tps features are available 5.906
And I shutdown Tails and wait for the computer to power off 2.519
# 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.869
After features/support/hooks.rb:339 0.372
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.464
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.443
And I log in to a new session 11.895
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.692
And I plug USB drive "to_upgrade" 2.283
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.244
Then the running Tails is installed on USB drive "to_upgrade" 17.662
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 2.056
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.886
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.153
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.635
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.225
And the expected persistent files created with the old Tails version are present in the filesystem 0.906
And all persistent directories from the old Tails version have safe access rights 1.677
After features/support/hooks.rb:339 0.914
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
3:33.187
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.144
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.028
And Tor is ready 12.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.097
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.865
Given I shutdown Tails and wait for the computer to power off 6.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.410
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.458
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.182
When the network is plugged 0.028
And Tor is ready 10.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.730
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.212
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.430
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.026
And Tor is ready 10.295
Then the Upgrader considers the system as up-to-date 0.094
# 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.576
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.748
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
18.598
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.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 7.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.181
After features/support/hooks.rb:339 0.526
After features/support/hooks.rb:108 0.000