Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 2 21 Apr 2026, 16:16

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:59.613 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:18.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.447
When I start Tails from USB drive "old" with network unplugged 1:0.201
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.669
After features/support/hooks.rb:100 0.069
Tags: @product
1:31.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 55.524
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 25.442
And I take note of which tps features are available 0.883
Then a Tails persistence partition exists on USB drive "old" 0.662
And I shutdown Tails and wait for the computer to power off 8.171
After features/support/hooks.rb:331 0.285
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.250
Then Tails is running from USB drive "old" 0.361
And all tps features are active 1.533
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.329
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.244
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.282
After features/support/hooks.rb:331 0.343
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.252
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.329
And I log in to a new session 13.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.838
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.304
Then the running Tails is installed on USB drive "to_upgrade" 16.015
And I unplug USB drive "to_upgrade" 0.173
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 2.113
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.285
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.127
Then all tps features from the old Tails version are active 1.117
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.949
After features/support/hooks.rb:331 0.942
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
4:45.282
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 8.193
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.023
And Tor is ready 22.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.144
Given I shutdown Tails and wait for the computer to power off 19.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.341
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.089
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.207
When the network is plugged 0.019
And Tor is ready 21.514
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.542
Given I shutdown Tails and wait for the computer to power off 17.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.336
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.020
And Tor is ready 22.481
Then the Upgrader considers the system as up-to-date 0.127
# 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.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
28.725
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.435
After features/support/hooks.rb:331 1.074
After features/support/hooks.rb:100 0.000