Project Number Date
test_Tails_ISO_stable 5731 23 Jun 2025, 12:49

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 20:45.647 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:6.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.066
When I start Tails from USB drive "old" with network unplugged 1:29.193
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.557
After features/support/hooks.rb:100 0.023
Tags: @product
2:22.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:32.081
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 39.125
And I take note of which tps features are available 1.791
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.497
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.508
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.873
Then Tails is running from USB drive "old" 0.504
And all tps features are active 1.995
When I write some files expected to persist 2.678
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.549
And all persistence configuration files have safe access rights 0.544
And all persistent directories from the old Tails version have safe access rights 3.116
And I take note of which tps features are available 0.525
And I shutdown Tails and wait for the computer to power off 4.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.912
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.742
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 without a persistent partition and stopped at Tails Greeter's login screen 12.050
And I log in to a new session 21.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.653
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.346
Then the running Tails is installed on USB drive "to_upgrade" 28.761
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:330 3.857
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.306
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.654
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.523
And the boot device has safe access rights 3.886
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:330 1.347
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:27.300
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 13.890
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
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.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.068
And Tor is ready 21.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.513
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.207
Given I shutdown Tails and wait for the computer to power off 11.814
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.503
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.045
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.351
When the network is plugged 0.056
And Tor is ready 19.128
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.806
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.372
Given I shutdown Tails and wait for the computer to power off 6.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.495
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.062
And Tor is ready 50.444
Then the Upgrader considers the system as up-to-date 0.369
# 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 16.179
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.839
After features/support/hooks.rb:330 0.782
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.226
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.769
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.061
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.766
After features/support/hooks.rb:330 2.051
After features/support/hooks.rb:100 0.000