Project Number Date
test_Tails_ISO_remove-boum.org 3 10 Sep 2026, 00:00

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:51.443 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:9.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.513
When I start Tails from USB drive "old" with network unplugged 52.052
Then the boot device has safe access rights 2.490
And Tails is running from USB drive "old" 0.177
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.100
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.555
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.798
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.607
And I take note of which tps features are available 7.218
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 4.026
After features/support/hooks.rb:339 0.291
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.256
Then Tails is running from USB drive "old" 0.220
And all tps features are active 8.173
When I write some files expected to persist 1.292
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 6.339
And I shutdown Tails and wait for the computer to power off 4.088
# 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.026
After features/support/hooks.rb:339 0.322
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.552
And I log in to a new session 13.070
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.692
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.500
Then the running Tails is installed on USB drive "to_upgrade" 17.986
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.842
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.867
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.142
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.044
Then all tps features from the old Tails version are active 1.200
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.397
And the expected persistent files created with the old Tails version are present in the filesystem 0.929
And all persistent directories from the old Tails version have safe access rights 1.924
After features/support/hooks.rb:339 0.846
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
3:55.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.536
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.550
When the network is plugged 0.038
And Tor is ready 11.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.914
Given I shutdown Tails and wait for the computer to power off 6.827
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.752
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 8.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.204
When the network is plugged 0.033
And Tor is ready 10.442
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.950
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.652
Given I shutdown Tails and wait for the computer to power off 2.734
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.710
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.544
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.035
And Tor is ready 10.174
Then the Upgrader considers the system as up-to-date 10.421
# 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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.466
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.000