Project Number Date
test_Tails_ISO_devel 4148 03 Jan 2026, 12:07

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:42.276 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:21.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 30.985
When I start Tails from USB drive "old" with network unplugged 45.712
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 3.515
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 58.973
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 26.658
And I take note of which tps features are available 1.176
Then a Tails persistence partition exists on USB drive "old" 0.682
And I shutdown Tails and wait for the computer to power off 3.169
After features/support/hooks.rb:331 0.368
After features/support/hooks.rb:100 0.009
Tags: @product
1:39.453
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.043
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.739
When I write some files expected to persist 1.466
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 2.047
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 7.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.288
After features/support/hooks.rb:331 0.411
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.295
And I log in to a new session 15.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 3.115
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.411
Then the running Tails is installed on USB drive "to_upgrade" 19.762
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 7.889
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.617
Then all tps features from the old Tails version are active 1.313
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.790
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.019
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:57.764
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 12.060
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.057
And Tor is ready 13.042
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.660
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.994
Given I shutdown Tails and wait for the computer to power off 11.009
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.865
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.933
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.223
When the network is plugged 0.059
And Tor is ready 11.934
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.489
Given I shutdown Tails and wait for the computer to power off 3.103
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.451
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.906
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.052
And Tor is ready 10.987
Then the Upgrader considers the system as up-to-date 0.138
# 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 5.347
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.468
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
21.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.186
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
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.059
And Tor is ready 10.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:331 0.901
After features/support/hooks.rb:100 0.000