Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 73 25 Jun 2026, 14:29

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:17.245 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:12.663
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.710
When I start Tails from USB drive "old" with network unplugged 53.958
Then the boot device has safe access rights 3.101
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 1.731
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.339
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.423
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 26.426
And I take note of which tps features are available 4.345
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 8.337
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.020
Tags: @product
1:43.210
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.720
Then Tails is running from USB drive "old" 0.236
And all tps features are active 4.904
When I write some files expected to persist 1.312
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.091
And I take note of which tps features are available 4.515
And I shutdown Tails and wait for the computer to power off 8.159
# 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.584
After features/support/hooks.rb:339 0.186
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.330
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.267
And I log in to a new session 16.254
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.159
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.328
Then the running Tails is installed on USB drive "to_upgrade" 14.791
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.746
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.627
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.629
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.172
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:339 0.641
After features/support/hooks.rb:108 0.006
3:56.322
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.107
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.013
And Tor is ready 13.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.938
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.452
Given I shutdown Tails and wait for the computer to power off 6.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.866
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.428
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.214
When the network is plugged 0.030
And Tor is ready 9.645
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.266
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.492
Given I shutdown Tails and wait for the computer to power off 7.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.075
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.539
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.014
And Tor is ready 9.723
Then the Upgrader considers the system as up-to-date 10.587
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 1.076
After features/support/hooks.rb:108 0.031
19.751
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.715
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
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.018
And Tor is ready 9.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.686
After features/support/hooks.rb:339 0.972
After features/support/hooks.rb:108 0.000