Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 82 05 Jul 2026, 14:27

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:47.625 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:13.047
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.104
When I start Tails from USB drive "old" with network unplugged 55.700
Then the boot device has safe access rights 2.510
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.490
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.793
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.276
And I take note of which tps features are available 3.950
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 8.258
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.729
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.420
Then Tails is running from USB drive "old" 0.200
And all tps features are active 4.514
When I write some files expected to persist 1.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.312
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 3.785
And I shutdown Tails and wait for the computer to power off 8.190
# 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.936
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.183
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 7.985
And I log in to a new session 11.830
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.861
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.202
Then the running Tails is installed on USB drive "to_upgrade" 14.777
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.895
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.645
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.889
Then all tps features from the old Tails version are active 0.882
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.568
And the expected persistent files created with the old Tails version are present in the filesystem 1.111
And all persistent directories from the old Tails version have safe access rights 1.916
After features/support/hooks.rb:339 0.493
After features/support/hooks.rb:108 0.005
3:50.181
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.931
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.015
And Tor is ready 13.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.802
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.257
Given I shutdown Tails and wait for the computer to power off 9.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.280
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.594
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.180
When the network is plugged 0.011
And Tor is ready 10.075
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.055
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 7.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.982
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.012
And Tor is ready 11.074
Then the Upgrader considers the system as up-to-date 10.532
# 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.765
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.010
20.692
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.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.064
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.000