Project Number Date
test_Tails_ISO_21548-flatpak-install 6 16 May 2026, 14:18

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:10.837 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:11.253
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.705
When I start Tails from USB drive "old" with network unplugged 54.085
Then the boot device has safe access rights 2.698
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 1.446
After features/support/hooks.rb:104 0.006
Tags: @product
1:20.614
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 52.659
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 24.130
And I take note of which tps features are available 0.346
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 2.674
After features/support/hooks.rb:335 0.239
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.519
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.992
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.082
When I write some files expected to persist 1.225
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.328
And all persistent directories from the old Tails version have safe access rights 1.730
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 7.964
# 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.588
After features/support/hooks.rb:335 0.308
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.394
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.081
And I log in to a new session 11.788
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.746
Then the running Tails is installed on USB drive "to_upgrade" 14.538
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 1.986
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.554
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.166
Then all tps features from the old Tails version are active 0.879
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.297
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.792
After features/support/hooks.rb:335 0.708
After features/support/hooks.rb:104 0.006
3:36.394
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.242
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.017
And Tor is ready 13.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.512
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.407
Given I shutdown Tails and wait for the computer to power off 6.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.018
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.363
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# 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.245
When the network is plugged 0.019
And Tor is ready 10.832
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.669
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.858
Given I shutdown Tails and wait for the computer to power off 8.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.789
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.175
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
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.195
When the network is plugged 0.015
And Tor is ready 9.952
Then the Upgrader considers the system as up-to-date 10.551
# 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 3.854
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:335 1.019
After features/support/hooks.rb:104 0.013
21.107
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.671
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.814
After features/support/hooks.rb:335 0.631
After features/support/hooks.rb:104 0.000