Project Number Date
test_Tails_ISO_devel 4441 11 Jun 2026, 07:47

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:22.242 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:3.474
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.706
When I start Tails from USB drive "old" with network unplugged 45.197
Then the boot device has safe access rights 2.749
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:335 3.651
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.063
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 54.346
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 25.449
And I take note of which tps features are available 0.419
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 2.949
After features/support/hooks.rb:335 0.360
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.934
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.988
Then Tails is running from USB drive "old" 0.214
And all tps features are active 1.250
When I write some files expected to persist 1.242
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.745
And I take note of which tps features are available 0.137
And I shutdown Tails and wait for the computer to power off 8.037
# 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" 11.822
After features/support/hooks.rb:335 0.430
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.786
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 7.835
And I log in to a new session 12.865
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.703
And I plug USB drive "to_upgrade" 2.274
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.445
Then the running Tails is installed on USB drive "to_upgrade" 15.378
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:335 2.285
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.961
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.653
Then all tps features from the old Tails version are active 1.087
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.576
And the expected persistent files created with the old Tails version are present in the filesystem 1.279
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:335 1.042
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
3:47.419
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.704
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.016
And Tor is ready 12.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.652
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.639
Given I shutdown Tails and wait for the computer to power off 10.926
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.010
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.205
When the network is plugged 0.020
And Tor is ready 10.839
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.826
Given I shutdown Tails and wait for the computer to power off 8.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.246
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.562
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.024
And Tor is ready 9.961
Then the Upgrader considers the system as up-to-date 10.577
# 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.372
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.453
After features/support/hooks.rb:335 1.099
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.603
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.968
After features/support/hooks.rb:335 0.676
After features/support/hooks.rb:104 0.000