Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 75 27 Jun 2026, 14:22

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:48.156 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.713
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.054
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" 13.276
When I start Tails from USB drive "old" with network unplugged 55.851
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.431
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.623
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.106
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 24.754
And I take note of which tps features are available 4.106
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 7.897
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.790
Then Tails is running from USB drive "old" 0.277
And all tps features are active 4.945
When I write some files expected to persist 1.201
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 1.896
And I take note of which tps features are available 3.649
And I shutdown Tails and wait for the computer to power off 7.766
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.779
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.708
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.929
And I log in to a new session 12.463
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.681
Then the running Tails is installed on USB drive "to_upgrade" 14.391
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.418
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.150
Then all tps features from the old Tails version are active 0.930
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.526
And the expected persistent files created with the old Tails version are present in the filesystem 1.024
And all persistent directories from the old Tails version have safe access rights 1.739
After features/support/hooks.rb:339 0.578
After features/support/hooks.rb:108 0.006
3:52.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.913
And no SquashFS delta is installed 0.048
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.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.020
And Tor is ready 13.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.302
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.715
Given I shutdown Tails and wait for the computer to power off 9.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.832
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.193
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.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.176
When the network is plugged 0.012
And Tor is ready 9.929
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.322
Given I shutdown Tails and wait for the computer to power off 7.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.499
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 5.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.018
And Tor is ready 10.640
Then the Upgrader considers the system as up-to-date 10.544
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:339 0.807
After features/support/hooks.rb:108 0.011
18.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 8.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.104
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.000