Project Number Date
test_Tails_ISO_devel 4440 10 Jun 2026, 11:24

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:9.338 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:7.406
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.206
When I start Tails from USB drive "old" with network unplugged 50.160
Then the boot device has safe access rights 2.283
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 3.689
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.714
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.179
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 24.723
And I take note of which tps features are available 0.296
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 6.638
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.542
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.276
Then Tails is running from USB drive "old" 0.206
And all tps features are active 1.260
When I write some files expected to persist 1.322
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.984
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 7.963
# 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.840
After features/support/hooks.rb:335 0.281
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.087
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.852
And I log in to a new session 11.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.718
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.316
Then the running Tails is installed on USB drive "to_upgrade" 14.848
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.000
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.488
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.872
Then all tps features from the old Tails version are active 0.870
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.040
And all persistent directories from the old Tails version have safe access rights 1.979
After features/support/hooks.rb:335 0.734
After features/support/hooks.rb:104 0.052
Tags: @product @automatic_upgrade
3:36.967
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.311
And no SquashFS delta is installed 0.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.016
And Tor is ready 12.776
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.774
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.344
Given I shutdown Tails and wait for the computer to power off 9.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.714
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.127
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.224
When the network is plugged 0.014
And Tor is ready 10.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.637
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.366
Given I shutdown Tails and wait for the computer to power off 7.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.404
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.014
And Tor is ready 11.106
Then the Upgrader considers the system as up-to-date 10.473
# 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.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:335 0.923
After features/support/hooks.rb:104 0.062
Tags: @product @automatic_upgrade
20.132
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.524
After features/support/hooks.rb:335 0.580
After features/support/hooks.rb:104 0.000