Project Number Date
test_Tails_ISO_21195-dont-include-unused-firmware 5 27 Jul 2026, 15: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 13:9.775 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:25.107
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 15.028
When I start Tails from USB drive "old" with network unplugged 1:5.223
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 1.959
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 1:0.320
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 27.632
And I take note of which tps features are available 4.617
Then a Tails persistence partition exists on USB drive "old" 0.655
And I shutdown Tails and wait for the computer to power off 6.237
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.006
Tags: @product
1:43.616
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.079
Then Tails is running from USB drive "old" 0.223
And all tps features are active 5.382
When I write some files expected to persist 1.917
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.481
And I take note of which tps features are available 4.021
And I shutdown Tails and wait for the computer to power off 4.030
# 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" 13.774
After features/support/hooks.rb:339 0.252
After features/support/hooks.rb:108 0.008
Tags: @product
2:17.431
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 without a persistent partition and stopped at Tails Greeter's login screen 8.833
And I log in to a new session 15.805
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.777
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.093
Then the running Tails is installed on USB drive "to_upgrade" 17.341
And I unplug USB drive "to_upgrade" 0.173
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:339 2.670
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.532
Then all tps features from the old Tails version are active 1.102
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.168
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.161
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
4:21.091
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 with a persistent partition enabled and logged in 8.591
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.017
And Tor is ready 14.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.879
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.448
Given I shutdown Tails and wait for the computer to power off 7.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.065
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.564
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.035
And Tor is ready 12.023
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.749
Given I shutdown Tails and wait for the computer to power off 4.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.569
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.731
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.014
And Tor is ready 11.609
Then the Upgrader considers the system as up-to-date 10.558
# 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 5.017
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.491
After features/support/hooks.rb:339 1.065
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.816
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 7.704
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 11.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.614
After features/support/hooks.rb:339 0.944
After features/support/hooks.rb:108 0.000