Project Number Date
test_Tails_ISO_devel 4343 14 Apr 2026, 14:18

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:43.175 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:6.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.024
When I start Tails from USB drive "old" with network unplugged 47.229
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.491
After features/support/hooks.rb:100 0.005
Tags: @product
1:26.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 56.117
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 24.804
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 4.160
After features/support/hooks.rb:331 0.630
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.580
Then Tails is running from USB drive "old" 0.290
And all tps features are active 1.272
When I write some files expected to persist 1.533
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 1.956
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.250
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.591
After features/support/hooks.rb:331 0.417
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.285
And I log in to a new session 13.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.004
Then the running Tails is installed on USB drive "to_upgrade" 16.933
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.693
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.838
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.338
After features/support/hooks.rb:331 0.835
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:45.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.747
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.019
And Tor is ready 21.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.830
Given I shutdown Tails and wait for the computer to power off 20.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.070
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.255
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
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.173
# 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.222
When the network is plugged 0.014
And Tor is ready 22.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.699
Given I shutdown Tails and wait for the computer to power off 17.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.767
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.292
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.025
And Tor is ready 20.881
Then the Upgrader considers the system as up-to-date 0.136
# 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.039
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.441
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
25.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.928
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 17.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.381
After features/support/hooks.rb:331 0.988
After features/support/hooks.rb:100 0.000