Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 15 09 May 2026, 13:59

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:57.295 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:7.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.973
When I start Tails from USB drive "old" with network unplugged 50.492
Then the boot device has safe access rights 2.588
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.531
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.333
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 23.815
And I take note of which tps features are available 0.729
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 3.974
After features/support/hooks.rb:331 0.255
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.331
Then Tails is running from USB drive "old" 0.213
And all tps features are active 1.177
When I write some files expected to persist 1.345
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.021
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 7.822
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.570
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.259
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 without a persistent partition and stopped at Tails Greeter's login screen 7.506
And I log in to a new session 11.577
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.772
Then the running Tails is installed on USB drive "to_upgrade" 15.218
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 2.094
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.064
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.748
Then all tps features from the old Tails version are active 0.888
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 2.410
And the expected persistent files created with the old Tails version are present in the filesystem 0.983
And all persistent directories from the old Tails version have safe access rights 1.778
After features/support/hooks.rb:331 0.721
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:26.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.033
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
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.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.015
And Tor is ready 21.728
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.016
Given I shutdown Tails and wait for the computer to power off 18.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.813
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.126
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.187
When the network is plugged 0.014
And Tor is ready 21.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.368
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.543
Given I shutdown Tails and wait for the computer to power off 17.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.882
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.061
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.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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.016
And Tor is ready 20.051
Then the Upgrader considers the system as up-to-date 0.109
# 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.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 16.806
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.000