Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 67 19 Jun 2026, 14:32

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:45.975 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:16.015
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.254
When I start Tails from USB drive "old" with network unplugged 58.182
Then the boot device has safe access rights 2.795
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.536
After features/support/hooks.rb:108 0.054
Tags: @product
1:29.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 52.963
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 24.376
And I take note of which tps features are available 3.944
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 6.830
After features/support/hooks.rb:339 0.339
After features/support/hooks.rb:108 0.018
Tags: @product
1:34.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.943
Then Tails is running from USB drive "old" 0.199
And all tps features are active 4.873
When I write some files expected to persist 1.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 1.841
And I take note of which tps features are available 3.424
And I shutdown Tails and wait for the computer to power off 6.893
# 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.783
After features/support/hooks.rb:339 0.452
After features/support/hooks.rb:108 0.017
Tags: @product
2:10.651
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.307
And I log in to a new session 13.539
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.739
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.368
Then the running Tails is installed on USB drive "to_upgrade" 14.199
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:339 2.494
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.332
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.848
Then all tps features from the old Tails version are active 0.863
And Tails is running from USB drive "to_upgrade" 0.232
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.029
And all persistent directories from the old Tails version have safe access rights 1.851
After features/support/hooks.rb:339 0.817
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:45.000
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.217
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.015
And Tor is ready 11.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.341
Given I shutdown Tails and wait for the computer to power off 5.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.627
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.771
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.258
When the network is plugged 0.014
And Tor is ready 10.939
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.518
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.618
Given I shutdown Tails and wait for the computer to power off 8.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.766
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.796
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.014
And Tor is ready 10.139
Then the Upgrader considers the system as up-to-date 10.507
# 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.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
20.070
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.775
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.000