Project Number Date
test_Tails_ISO_stable 6730 08 Oct 2026, 11:32

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 10:59.760 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:4.830
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.115
When I start Tails from USB drive "old" with network unplugged 47.980
Then the boot device has safe access rights 2.003
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.836
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.571
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 22.426
And I take note of which tps features are available 6.095
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 4.027
After features/support/hooks.rb:339 0.291
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.993
Then Tails is running from USB drive "old" 0.181
And all tps features are active 6.806
When I write some files expected to persist 0.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.236
And all persistent directories from the old Tails version have safe access rights 1.367
And I take note of which tps features are available 6.042
And I shutdown Tails and wait for the computer to power off 2.538
# 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.277
After features/support/hooks.rb:339 0.207
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.871
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.058
And I log in to a new session 11.044
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.602
And I plug USB drive "to_upgrade" 2.178
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.757
Then the running Tails is installed on USB drive "to_upgrade" 17.951
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 1.510
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.705
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.104
Then all tps features from the old Tails version are active 0.931
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 2.046
And the expected persistent files created with the old Tails version are present in the filesystem 0.900
And all persistent directories from the old Tails version have safe access rights 1.469
After features/support/hooks.rb:339 0.450
After features/support/hooks.rb:108 0.005
3:22.074
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.857
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
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.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.031
And Tor is ready 13.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.054
Given I shutdown Tails and wait for the computer to power off 6.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.350
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.147
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.080
# 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.139
When the network is plugged 0.025
And Tor is ready 10.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.343
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.473
Given I shutdown Tails and wait for the computer to power off 2.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.259
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.365
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.029
And Tor is ready 10.520
Then the Upgrader considers the system as up-to-date 0.094
# 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 2.975
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.284
After features/support/hooks.rb:339 0.769
After features/support/hooks.rb:108 0.009
30.680
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 20.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.021
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 8.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.491
After features/support/hooks.rb:339 0.980
After features/support/hooks.rb:108 0.000