Project Number Date
test_Tails_ISO_devel 4101 05 Dec 2025, 07:01

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 18:51.873 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
2:4.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.833
When I start Tails from USB drive "old" with network unplugged 1:26.711
Then the boot device has safe access rights 3.545
And Tails is running from USB drive "old" 0.440
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 3.992
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login 1:32.737
Then Tails is running from USB drive "old" 0.641
And I create a persistent partition 37.723
And I take note of which tps features are available 6.087
Then a Tails persistence partition exists on USB drive "old" 0.678
And I shutdown Tails and wait for the computer to power off 8.948
After features/support/hooks.rb:331 0.586
After features/support/hooks.rb:100 0.011
Tags: @product
3:22.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 6.366
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.867
Then Tails is running from USB drive "old" 0.690
And all tps features are active 10.306
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.339
And I take note of which tps features are available 24.347
And I shutdown Tails and wait for the computer to power off 12.144
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.194
After features/support/hooks.rb:331 0.640
After features/support/hooks.rb:100 0.023
Tags: @product
3:22.077
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 without a persistent partition and stopped at Tails Greeter's login screen 30.288
And I log in to a new session 24.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.608
And I plug USB drive "to_upgrade" 2.696
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.587
Then the running Tails is installed on USB drive "to_upgrade" 21.982
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:331 4.139
After features/support/hooks.rb:100 0.000
Tags: @product
1:39.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:30.309
Then all tps features from the old Tails version are active 2.160
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.299
After features/support/hooks.rb:331 0.957
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:28.875
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 15.477
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.388
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.543
When the network is plugged 0.322
And Tor is ready 43.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.102
Given I shutdown Tails and wait for the computer to power off 12.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.946
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 28.862
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
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.168
# 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.234
When the network is plugged 0.322
And Tor is ready 12.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.766
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.146
Given I shutdown Tails and wait for the computer to power off 7.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.533
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.799
And the file system changes introduced in version 6.3~testoverlayfs are present 0.644
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.234
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.075
And Tor is ready 11.831
Then the Upgrader considers the system as up-to-date 0.127
# 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 6.379
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.272
After features/support/hooks.rb:331 1.080
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
26.549
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 11.305
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.137
And Tor is ready 14.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
After features/support/hooks.rb:331 0.978
After features/support/hooks.rb:100 0.000