Project Number Date
test_Tails_ISO_devel 4654 02 Oct 2026, 11:17

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:15.682 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
57.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.419
When I start Tails from USB drive "old" with network unplugged 39.870
Then the boot device has safe access rights 2.425
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.627
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.324
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 48.129
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 23.203
And I take note of which tps features are available 7.009
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 4.147
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.128
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.648
Then Tails is running from USB drive "old" 0.186
And all tps features are active 7.489
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.594
And I take note of which tps features are available 5.965
And I shutdown Tails and wait for the computer to power off 2.546
# 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.969
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.014
Tags: @product
2:11.358
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.572
And I log in to a new session 10.931
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.702
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.748
Then the running Tails is installed on USB drive "to_upgrade" 17.981
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.686
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.661
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 1:1.783
Then all tps features from the old Tails version are active 1.040
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.554
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 1.819
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.006
3:30.071
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.252
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.032
And Tor is ready 13.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.307
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.713
Given I shutdown Tails and wait for the computer to power off 5.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.086
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.490
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.231
When the network is plugged 0.024
And Tor is ready 10.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.519
Given I shutdown Tails and wait for the computer to power off 2.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.612
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.861
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.030
And Tor is ready 10.323
Then the Upgrader considers the system as up-to-date 0.087
# 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.512
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.011
31.656
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 20.950
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.992
After features/support/hooks.rb:339 0.472
After features/support/hooks.rb:108 0.000