Project Number Date
test_Tails_ISO_stable 6493 09 Jul 2026, 07:38

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:6.082 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:8.209
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.746
When I start Tails from USB drive "old" with network unplugged 49.632
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 1.418
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login 54.366
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 24.242
And I take note of which tps features are available 4.311
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 4.285
After features/support/hooks.rb:339 0.201
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.438
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.527
Then Tails is running from USB drive "old" 0.328
And all tps features are active 5.552
When I write some files expected to persist 1.499
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.789
And I take note of which tps features are available 3.923
And I shutdown Tails and wait for the computer to power off 8.056
# 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.191
After features/support/hooks.rb:339 0.386
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.615
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 without a persistent partition and stopped at Tails Greeter's login screen 8.020
And I log in to a new session 12.360
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.035
Then the running Tails is installed on USB drive "to_upgrade" 14.968
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.663
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.891
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.179
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.431
And the boot device has safe access rights 2.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.282
And all persistent directories from the old Tails version have safe access rights 2.048
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
4:2.113
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.271
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.017
And Tor is ready 14.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.340
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.754
Given I shutdown Tails and wait for the computer to power off 8.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.245
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.439
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.220
When the network is plugged 0.015
And Tor is ready 11.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.458
Given I shutdown Tails and wait for the computer to power off 8.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.600
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.555
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.016
And Tor is ready 10.235
Then the Upgrader considers the system as up-to-date 10.705
# 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.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.975
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
20.564
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.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.581
After features/support/hooks.rb:339 0.644
After features/support/hooks.rb:108 0.000