Project Number Date
test_Tails_ISO_stable 6534 27 Jul 2026, 13:51

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 12:25.686 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:18.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.277
When I start Tails from USB drive "old" with network unplugged 59.560
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:339 1.463
After features/support/hooks.rb:108 0.009
Tags: @product
1:30.274
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 55.333
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 25.781
And I take note of which tps features are available 4.129
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.095
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.008
Tags: @product
1:43.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.914
Then Tails is running from USB drive "old" 0.268
And all tps features are active 5.729
When I write some files expected to persist 1.425
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.362
And I take note of which tps features are available 4.792
And I shutdown Tails and wait for the computer to power off 4.133
# 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.900
After features/support/hooks.rb:339 0.210
After features/support/hooks.rb:108 0.010
Tags: @product
2:14.262
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.497
And I log in to a new session 14.432
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.916
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.165
Then the running Tails is installed on USB drive "to_upgrade" 15.684
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.357
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.551
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.434
Then all tps features from the old Tails version are active 1.141
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.597
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 1.953
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:1.323
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.633
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.018
And Tor is ready 13.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.123
Given I shutdown Tails and wait for the computer to power off 6.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.990
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 5.640
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.244
When the network is plugged 0.019
And Tor is ready 10.563
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.857
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.868
Given I shutdown Tails and wait for the computer to power off 4.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.248
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 5.706
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.014
And Tor is ready 11.304
Then the Upgrader considers the system as up-to-date 10.548
# 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 4.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 0.814
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
21.570
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 8.521
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.018
And Tor is ready 11.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.381
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.000