Project Number Date
test_Tails_ISO_devel 4282 16 Mar 2026, 07:55

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:59.387 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:11.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.060
When I start Tails from USB drive "old" with network unplugged 52.149
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.572
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 57.821
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.999
And I take note of which tps features are available 0.748
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 7.120
After features/support/hooks.rb:331 0.203
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.377
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.296
When I write some files expected to persist 1.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 1.911
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 3.998
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.853
After features/support/hooks.rb:331 0.400
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.283
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.883
And I log in to a new session 13.182
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.982
Then the running Tails is installed on USB drive "to_upgrade" 17.004
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 3.582
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.994
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.950
And the expected persistent files created with the old Tails version are present in the filesystem 1.179
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:52.560
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 with a persistent partition enabled and logged in 8.867
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.026
And Tor is ready 31.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.938
Given I shutdown Tails and wait for the computer to power off 20.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.002
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# 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.198
When the network is plugged 0.014
And Tor is ready 22.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.365
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.527
Given I shutdown Tails and wait for the computer to power off 17.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.437
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.015
And Tor is ready 20.642
Then the Upgrader considers the system as up-to-date 0.084
# 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.137
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.962
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.372
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 0.848
After features/support/hooks.rb:100 0.000