Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 8 03 May 2026, 22:46

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:44.452 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:1.501
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.858
When I start Tails from USB drive "old" with network unplugged 44.314
Then the boot device has safe access rights 2.604
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.268
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 50.489
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.115
And I take note of which tps features are available 0.669
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 8.146
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.998
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.528
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.026
When I write some files expected to persist 1.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 8.172
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.842
After features/support/hooks.rb:331 0.296
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.868
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 without a persistent partition and stopped at Tails Greeter's login screen 7.625
And I log in to a new session 11.248
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.843
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.590
Then the running Tails is installed on USB drive "to_upgrade" 15.024
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 1.838
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.579
Then all tps features from the old Tails version are active 0.933
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.393
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.859
After features/support/hooks.rb:331 0.676
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:15.594
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.063
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.014
And Tor is ready 20.369
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.287
Given I shutdown Tails and wait for the computer to power off 19.778
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.235
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.067
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.014
And Tor is ready 19.880
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.150
Given I shutdown Tails and wait for the computer to power off 7.839
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.129
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.187
When the network is plugged 0.015
And Tor is ready 21.086
Then the Upgrader considers the system as up-to-date 0.126
# 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.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:331 0.742
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.134
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.389
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.442
After features/support/hooks.rb:331 0.608
After features/support/hooks.rb:100 0.000