Project Number Date
test_Tails_ISO_21565-flatpak-safe-flatpak 1 17 Nov 2026, 20:53

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 12:27.373 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:24.522
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.649
When I start Tails from USB drive "old" with network unplugged 1:5.178
Then the boot device has safe access rights 2.753
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 1.394
After features/support/hooks.rb:108 0.040
Tags: @product
1:32.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 52.107
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 26.622
And I take note of which tps features are available 7.818
Then a Tails persistence partition exists on USB drive "old" 0.641
And I shutdown Tails and wait for the computer to power off 4.399
After features/support/hooks.rb:339 0.311
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.374
Then Tails is running from USB drive "old" 0.218
And all tps features are active 8.418
When I write some files expected to persist 1.576
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 1.962
And I take note of which tps features are available 6.311
And I shutdown Tails and wait for the computer to power off 4.007
# 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" 12.135
After features/support/hooks.rb:339 0.214
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.402
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 8.839
And I log in to a new session 12.127
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.891
And I plug USB drive "to_upgrade" 2.283
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.236
Then the running Tails is installed on USB drive "to_upgrade" 19.765
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.842
After features/support/hooks.rb:108 0.000
Tags: @product
1:18.034
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.879
Then all tps features from the old Tails version are active 1.172
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.551
And the expected persistent files created with the old Tails version are present in the filesystem 1.680
And all persistent directories from the old Tails version have safe access rights 2.428
After features/support/hooks.rb:339 0.770
After features/support/hooks.rb:108 0.031
3:55.096
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.563
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.035
And Tor is ready 13.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.836
Given I shutdown Tails and wait for the computer to power off 7.078
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.345
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.978
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.194
When the network is plugged 0.026
And Tor is ready 11.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.281
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.783
Given I shutdown Tails and wait for the computer to power off 5.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.015
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 9.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.023
And Tor is ready 10.856
Then the Upgrader considers the system as up-to-date 0.096
# 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.288
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.009
20.642
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 8.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 8.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.157
After features/support/hooks.rb:339 0.512
After features/support/hooks.rb:108 0.000