Project Number Date
test_Tails_ISO_remove-boum.org 2 09 Sep 2026, 20:33

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:5.380 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.889
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.467
When I start Tails from USB drive "old" with network unplugged 52.270
Then the boot device has safe access rights 2.325
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 1.290
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 50.653
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.486
And I take note of which tps features are available 6.852
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 3.974
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.539
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.562
Then Tails is running from USB drive "old" 0.218
And all tps features are active 6.992
When I write some files expected to persist 1.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.220
And all persistent directories from the old Tails version have safe access rights 2.241
And I take note of which tps features are available 6.880
And I shutdown Tails and wait for the computer to power off 2.639
# 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.400
After features/support/hooks.rb:339 0.302
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.144
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 without a persistent partition and stopped at Tails Greeter's login screen 8.876
And I log in to a new session 12.771
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.689
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.983
Then the running Tails is installed on USB drive "to_upgrade" 19.329
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 2.377
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.208
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.775
Then all tps features from the old Tails version are active 1.216
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.447
And the expected persistent files created with the old Tails version are present in the filesystem 0.946
And all persistent directories from the old Tails version have safe access rights 1.515
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:2.515
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 21.844
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.031
And Tor is ready 11.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.724
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.056
Given I shutdown Tails and wait for the computer to power off 5.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.892
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.804
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.235
When the network is plugged 0.029
And Tor is ready 10.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.706
Given I shutdown Tails and wait for the computer to power off 3.877
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.908
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.649
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.159
When the network is plugged 0.029
And Tor is ready 10.626
Then the Upgrader considers the system as up-to-date 10.481
# 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.689
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.520
After features/support/hooks.rb:339 0.826
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
20.297
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.034
And Tor is ready 9.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.655
After features/support/hooks.rb:339 0.869
After features/support/hooks.rb:108 0.000