Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 78 30 Jun 2026, 14:36

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:53.809 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:27.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.936
When I start Tails from USB drive "old" with network unplugged 1:7.716
Then the boot device has safe access rights 2.805
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 1.380
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.940
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 53.682
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 24.851
And I take note of which tps features are available 4.197
Then a Tails persistence partition exists on USB drive "old" 0.596
And I shutdown Tails and wait for the computer to power off 8.282
After features/support/hooks.rb:339 0.404
After features/support/hooks.rb:108 0.015
Tags: @product
1:35.020
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.741
Then Tails is running from USB drive "old" 0.332
And all tps features are active 4.430
When I write some files expected to persist 1.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 4.151
And I shutdown Tails and wait for the computer to power off 8.098
# 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.674
After features/support/hooks.rb:339 0.297
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.706
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.074
And I log in to a new session 12.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.866
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.123
Then the running Tails is installed on USB drive "to_upgrade" 14.785
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.422
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.667
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.044
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.079
Then all tps features from the old Tails version are active 0.915
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.314
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
3:42.070
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.722
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.014
And Tor is ready 11.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.596
Given I shutdown Tails and wait for the computer to power off 9.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.731
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.847
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.201
When the network is plugged 0.017
And Tor is ready 9.654
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.172
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.781
Given I shutdown Tails and wait for the computer to power off 2.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.327
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.830
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.179
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.752
Then the Upgrader considers the system as up-to-date 10.512
# 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.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.177
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.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.094
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.000