Project Number Date
test_Tails_ISO_devel 4152 05 Jan 2026, 20:28

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:28.920 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.081
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.727
When I start Tails from USB drive "old" with network unplugged 52.852
Then the boot device has safe access rights 2.662
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 3.530
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 54.407
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 25.410
And I take note of which tps features are available 0.838
Then a Tails persistence partition exists on USB drive "old" 0.602
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:331 0.519
After features/support/hooks.rb:100 0.007
Tags: @product
1:20.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.688
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.044
When I write some files expected to persist 1.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.952
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 2.728
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.449
After features/support/hooks.rb:331 0.434
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.921
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.999
And I log in to a new session 12.341
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.803
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.243
Then the running Tails is installed on USB drive "to_upgrade" 15.947
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 3.730
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.813
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.480
And the expected persistent files created with the old Tails version are present in the filesystem 1.123
And all persistent directories from the old Tails version have safe access rights 1.991
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:43.870
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.769
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
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.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.023
And Tor is ready 12.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.588
Given I shutdown Tails and wait for the computer to power off 9.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.084
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.182
When the network is plugged 0.018
And Tor is ready 11.319
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.811
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.158
Given I shutdown Tails and wait for the computer to power off 8.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.475
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.034
And Tor is ready 11.546
Then the Upgrader considers the system as up-to-date 10.601
# 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.398
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:331 1.089
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
20.591
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.038
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.528
After features/support/hooks.rb:331 0.688
After features/support/hooks.rb:100 0.000