Project Number Date
test_Tails_ISO_21195-dont-include-unused-firmware 2 25 Jul 2026, 02:35

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:32.823 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:16.921
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.194
When I start Tails from USB drive "old" with network unplugged 59.543
Then the boot device has safe access rights 2.428
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.641
After features/support/hooks.rb:108 0.042
Tags: @product
1:25.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.887
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.320
And I take note of which tps features are available 3.779
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 4.049
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.213
Then Tails is running from USB drive "old" 0.223
And all tps features are active 4.778
When I write some files expected to persist 1.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 1.738
And I take note of which tps features are available 3.600
And I shutdown Tails and wait for the computer to power off 4.225
# 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.640
After features/support/hooks.rb:339 0.317
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.705
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.991
And I log in to a new session 13.142
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.567
Then the running Tails is installed on USB drive "to_upgrade" 14.686
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.007
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.508
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
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.895
Then all tps features from the old Tails version are active 0.940
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.350
And the expected persistent files created with the old Tails version are present in the filesystem 1.087
And all persistent directories from the old Tails version have safe access rights 1.979
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.174
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.806
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.013
And Tor is ready 13.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.948
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.726
Given I shutdown Tails and wait for the computer to power off 6.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.688
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.769
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.205
When the network is plugged 0.013
And Tor is ready 9.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.758
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 4.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.624
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.712
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.015
And Tor is ready 9.695
Then the Upgrader considers the system as up-to-date 10.503
# 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.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.757
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.523
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.496
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.017
And Tor is ready 10.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.376
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.000