Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 14 08 May 2026, 14:24

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 12:48.031 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:10.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 13.671
When I start Tails from USB drive "old" with network unplugged 51.882
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.490
After features/support/hooks.rb:100 0.061
Tags: @product
1:30.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 55.865
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.541
And I take note of which tps features are available 0.720
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:331 0.232
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.200
Then Tails is running from USB drive "old" 0.251
And all tps features are active 1.261
When I write some files expected to persist 1.403
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.015
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 8.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.403
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.133
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 without a persistent partition and stopped at Tails Greeter's login screen 7.509
And I log in to a new session 13.921
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.312
Then the running Tails is installed on USB drive "to_upgrade" 16.011
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:331 2.470
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.134
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.509
And the expected persistent files created with the old Tails version are present in the filesystem 1.311
And all persistent directories from the old Tails version have safe access rights 1.931
After features/support/hooks.rb:331 0.698
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:43.533
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.527
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.014
And Tor is ready 20.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.647
Given I shutdown Tails and wait for the computer to power off 18.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.853
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.218
When the network is plugged 0.015
And Tor is ready 20.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.278
Given I shutdown Tails and wait for the computer to power off 17.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.744
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.046
And Tor is ready 21.198
Then the Upgrader considers the system as up-to-date 0.110
# 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.946
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:331 1.050
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.683
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 20.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.000