Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 12 07 May 2026, 14:39

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 13:23.803 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:13.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 14.832
When I start Tails from USB drive "old" with network unplugged 53.246
Then the boot device has safe access rights 3.216
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 2.039
After features/support/hooks.rb:100 0.017
Tags: @product
1:35.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login 58.671
Then Tails is running from USB drive "old" 1.403
And I create a persistent partition 25.349
And I take note of which tps features are available 0.969
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 8.280
After features/support/hooks.rb:331 0.485
After features/support/hooks.rb:100 0.008
Tags: @product
1:36.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.938
Then Tails is running from USB drive "old" 0.482
And all tps features are active 1.426
When I write some files expected to persist 1.569
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.281
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 8.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.276
After features/support/hooks.rb:331 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.588
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 8.385
And I log in to a new session 13.873
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.998
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.932
Then the running Tails is installed on USB drive "to_upgrade" 18.829
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 2.096
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.303
Then all tps features from the old Tails version are active 1.249
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.058
And the expected persistent files created with the old Tails version are present in the filesystem 1.173
And all persistent directories from the old Tails version have safe access rights 2.400
After features/support/hooks.rb:331 0.664
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:55.156
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.439
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.015
And Tor is ready 22.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.450
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.002
Given I shutdown Tails and wait for the computer to power off 19.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.397
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.255
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
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.155
# 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.215
When the network is plugged 0.015
And Tor is ready 22.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.759
Given I shutdown Tails and wait for the computer to power off 18.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.035
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.255
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.027
And Tor is ready 22.515
Then the Upgrader considers the system as up-to-date 0.143
# 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 5.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
28.507
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.754
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.474
After features/support/hooks.rb:331 0.794
After features/support/hooks.rb:100 0.000