Project Number Date
test_Tails_ISO_21578-test-suite-pure-disk-boot 2 16 Jun 2026, 02:49

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:21.622 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:14.366
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.520
When I start Tails from USB drive "old" with network unplugged 55.753
Then the boot device has safe access rights 3.044
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.717
After features/support/hooks.rb:108 0.021
Tags: @product
1:32.240
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login 55.388
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 24.235
And I take note of which tps features are available 4.338
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 7.218
After features/support/hooks.rb:339 0.200
After features/support/hooks.rb:108 0.018
Tags: @product
1:40.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.360
Then Tails is running from USB drive "old" 0.262
And all tps features are active 4.931
When I write some files expected to persist 1.436
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.915
And I take note of which tps features are available 4.483
And I shutdown Tails and wait for the computer to power off 6.985
# 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" 12.484
After features/support/hooks.rb:339 0.350
After features/support/hooks.rb:108 0.018
Tags: @product
2:11.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.087
And I log in to a new session 12.719
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.039
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.581
Then the running Tails is installed on USB drive "to_upgrade" 15.531
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 2.241
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.124
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.131
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.122
Then all tps features from the old Tails version are active 0.951
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.634
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.945
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.049
4:4.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.557
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
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.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.018
And Tor is ready 12.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.333
Given I shutdown Tails and wait for the computer to power off 9.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.743
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.609
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.197
When the network is plugged 0.059
And Tor is ready 11.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.272
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.169
Given I shutdown Tails and wait for the computer to power off 8.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.160
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.591
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.017
And Tor is ready 12.386
Then the Upgrader considers the system as up-to-date 10.491
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:339 0.746
After features/support/hooks.rb:108 0.037
22.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.321
After features/support/hooks.rb:339 1.130
After features/support/hooks.rb:108 0.000