Project Number Date
test_Tails_ISO_devel 4231 14 Feb 2026, 12:05

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.863 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:1.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.393
When I start Tails from USB drive "old" with network unplugged 42.788
Then the boot device has safe access rights 2.651
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.539
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 54.616
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.973
And I take note of which tps features are available 0.815
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 7.077
After features/support/hooks.rb:331 0.579
After features/support/hooks.rb:100 0.011
Tags: @product
1:25.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.988
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.207
When I write some files expected to persist 1.320
# 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.318
And all persistent directories from the old Tails version have safe access rights 1.896
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 4.086
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.190
After features/support/hooks.rb:331 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.272
And I log in to a new session 12.646
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.701
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.174
Then the running Tails is installed on USB drive "to_upgrade" 17.445
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:331 8.072
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.608
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 2.829
And the expected persistent files created with the old Tails version are present in the filesystem 1.248
And all persistent directories from the old Tails version have safe access rights 2.293
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:19.241
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 9.584
And no SquashFS delta is installed 0.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
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.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.023
And Tor is ready 14.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.218
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.036
Given I shutdown Tails and wait for the computer to power off 18.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.357
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.207
When the network is plugged 0.015
And Tor is ready 11.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.988
Given I shutdown Tails and wait for the computer to power off 8.129
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.113
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.262
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.015
And Tor is ready 39.507
Then the Upgrader considers the system as up-to-date 0.146
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.432
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.751
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 7.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.165
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.000