Project Number Date
test_Tails_ISO_devel 4120 13 Dec 2025, 12:29

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 16:52.091 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:43.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 32.345
When I start Tails from USB drive "old" with network unplugged 1:5.665
Then the boot device has safe access rights 3.491
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:331 3.586
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:10.381
Then Tails is running from USB drive "old" 0.690
And I create a persistent partition 37.398
And I take note of which tps features are available 6.225
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 12.652
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.009
Tags: @product
3:15.895
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 10.885
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.056
Then Tails is running from USB drive "old" 1.553
And all tps features are active 3.111
When I write some files expected to persist 1.655
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.258
And I take note of which tps features are available 20.996
And I shutdown Tails and wait for the computer to power off 11.238
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.471
After features/support/hooks.rb:331 0.306
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.081
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 13.209
And I log in to a new session 17.749
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.149
And I plug USB drive "to_upgrade" 4.304
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.727
Then the running Tails is installed on USB drive "to_upgrade" 21.236
And I unplug USB drive "to_upgrade" 0.483
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:331 4.065
After features/support/hooks.rb:100 0.000
Tags: @product
1:36.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:26.698
Then all tps features from the old Tails version are active 1.960
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.748
And all persistent directories from the old Tails version have safe access rights 2.211
After features/support/hooks.rb:331 1.004
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:43.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.506
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.056
And Tor is ready 16.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.945
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.333
Given I shutdown Tails and wait for the computer to power off 12.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.574
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.405
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.213
# 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.525
When the network is plugged 0.469
And Tor is ready 12.042
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.703
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.872
Given I shutdown Tails and wait for the computer to power off 8.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.484
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.327
And the file system changes introduced in version 6.3~testoverlayfs are present 0.430
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.061
And Tor is ready 11.859
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 9.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.450
After features/support/hooks.rb:331 1.724
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
27.337
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 with a persistent partition enabled and logged in 12.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
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.053
And Tor is ready 11.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.047
After features/support/hooks.rb:331 1.205
After features/support/hooks.rb:100 0.000