Project Number Date
test_Tails_ISO_devel 4051 03 Nov 2025, 21:12

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 17:11.441 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:51.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.061
When I start Tails from USB drive "old" with network unplugged 1:14.499
Then the boot device has safe access rights 3.194
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:331 3.902
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:25.049
Then Tails is running from USB drive "old" 0.535
And I create a persistent partition 43.126
And I take note of which tps features are available 1.067
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 7.930
After features/support/hooks.rb:331 0.441
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.562
Then Tails is running from USB drive "old" 0.734
And all tps features are active 1.997
When I write some files expected to persist 1.598
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.867
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 7.807
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.571
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.343
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 12.232
And I log in to a new session 16.368
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.474
And I plug USB drive "to_upgrade" 3.066
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.759
Then the running Tails is installed on USB drive "to_upgrade" 21.995
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:331 4.296
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.135
Then all tps features from the old Tails version are active 2.146
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.488
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.550
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
5:48.885
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 13.372
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
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.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.060
And Tor is ready 44.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.833
Given I shutdown Tails and wait for the computer to power off 11.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.607
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.340
When the network is plugged 0.057
And Tor is ready 12.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.925
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.427
Given I shutdown Tails and wait for the computer to power off 7.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.695
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.856
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.243
When the network is plugged 0.058
And Tor is ready 12.305
Then the Upgrader considers the system as up-to-date 0.217
# 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.542
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.513
After features/support/hooks.rb:331 0.988
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
25.009
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 11.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
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.062
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 12.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.597
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.000