Project Number Date
test_Tails_ISO_devel 4407 21 May 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:58.220 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:15.903
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.712
When I start Tails from USB drive "old" with network unplugged 56.695
Then the boot device has safe access rights 2.728
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 1.250
After features/support/hooks.rb:104 0.009
Tags: @product
1:30.531
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 56.676
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 25.631
And I take note of which tps features are available 0.326
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 7.075
After features/support/hooks.rb:335 0.336
After features/support/hooks.rb:104 0.015
Tags: @product
1:28.701
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.656
Then Tails is running from USB drive "old" 0.264
And all tps features are active 1.371
When I write some files expected to persist 1.261
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.135
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 4.186
# 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.999
After features/support/hooks.rb:335 0.148
After features/support/hooks.rb:104 0.009
Tags: @product
2:14.563
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.525
And I log in to a new session 13.006
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.916
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.928
Then the running Tails is installed on USB drive "to_upgrade" 16.600
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:335 3.658
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.446
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.027
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 3.308
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:335 0.914
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:53.658
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.612
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.017
And Tor is ready 14.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.563
Given I shutdown Tails and wait for the computer to power off 10.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.701
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.434
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.242
When the network is plugged 0.018
And Tor is ready 11.684
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.694
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.729
Given I shutdown Tails and wait for the computer to power off 8.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.935
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.016
And Tor is ready 11.742
Then the Upgrader considers the system as up-to-date 10.576
# 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.499
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.746
After features/support/hooks.rb:335 0.863
After features/support/hooks.rb:104 0.048
Tags: @product @automatic_upgrade
20.415
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.503
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.262
After features/support/hooks.rb:335 0.949
After features/support/hooks.rb:104 0.000