Project Number Date
test_Tails_ISO_stable 6433 07 Jun 2026, 11:37

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:14.320 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:0.350
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.344
When I start Tails from USB drive "old" with network unplugged 42.358
Then the boot device has safe access rights 2.660
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:335 1.483
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.131
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 53.650
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.373
And I take note of which tps features are available 0.352
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 6.826
After features/support/hooks.rb:335 0.247
After features/support/hooks.rb:104 0.007
Tags: @product
1:23.567
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.834
Then Tails is running from USB drive "old" 0.226
And all tps features are active 1.073
When I write some files expected to persist 1.297
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.837
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 4.083
# 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.541
After features/support/hooks.rb:335 0.332
After features/support/hooks.rb:104 0.006
Tags: @product
2:11.419
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 without a persistent partition and stopped at Tails Greeter's login screen 8.003
And I log in to a new session 13.168
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.845
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.576
Then the running Tails is installed on USB drive "to_upgrade" 15.322
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.019
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.423
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.637
Then all tps features from the old Tails version are active 0.972
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.060
And all persistent directories from the old Tails version have safe access rights 2.104
After features/support/hooks.rb:335 0.798
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:40.775
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 with a persistent partition enabled and logged in 8.395
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.015
And Tor is ready 13.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.784
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.063
Given I shutdown Tails and wait for the computer to power off 6.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.333
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.458
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.200
When the network is plugged 0.023
And Tor is ready 10.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.502
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.239
Given I shutdown Tails and wait for the computer to power off 8.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.921
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.203
When the network is plugged 0.016
And Tor is ready 10.303
Then the Upgrader considers the system as up-to-date 10.574
# 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.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:335 0.687
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.651
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.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.842
After features/support/hooks.rb:335 0.539
After features/support/hooks.rb:104 0.000