Project Number Date
test_Tails_ISO_stable 6086 22 Jan 2026, 17:19

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 14:18.173 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:46.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 39.185
When I start Tails from USB drive "old" with network unplugged 1:2.282
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:331 3.778
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:4.800
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 28.930
And I take note of which tps features are available 1.179
Then a Tails persistence partition exists on USB drive "old" 0.680
And I shutdown Tails and wait for the computer to power off 7.687
After features/support/hooks.rb:331 0.240
After features/support/hooks.rb:100 0.009
Tags: @product
1:51.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.023
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.114
When I write some files expected to persist 1.401
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.486
And all persistent directories from the old Tails version have safe access rights 2.494
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 7.667
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.228
After features/support/hooks.rb:331 0.347
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.935
And I log in to a new session 13.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.515
And I plug USB drive "to_upgrade" 2.961
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.512
Then the running Tails is installed on USB drive "to_upgrade" 22.132
And I unplug USB drive "to_upgrade" 0.679
And I unplug USB drive "__internal" 2.054
After features/support/hooks.rb:331 5.423
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.127
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.047
Then all tps features from the old Tails version are active 1.554
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.065
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:15.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.004
And no SquashFS delta is installed 0.090
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.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.050
And Tor is ready 13.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.801
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.676
Given I shutdown Tails and wait for the computer to power off 12.953
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.171
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.188
# 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.246
When the network is plugged 0.056
And Tor is ready 12.089
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.708
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.208
Given I shutdown Tails and wait for the computer to power off 7.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.368
Then Tails is running version 6.3~testoverlayfs 0.045
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.063
And Tor is ready 12.488
Then the Upgrader considers the system as up-to-date 0.115
# 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 5.839
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.532
After features/support/hooks.rb:331 1.090
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
23.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.472
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 11.015
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.641
After features/support/hooks.rb:331 1.069
After features/support/hooks.rb:100 0.000