Project Number Date
test_Tails_ISO_test-suite-options 25 14 Jul 2025, 20:24

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 21:23.494 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:23.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.202
When I start Tails from USB drive "old" with network unplugged 1:46.242
Then the boot device has safe access rights 3.814
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 1.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:37.852
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 35.728
And I take note of which tps features are available 2.999
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.572
After features/support/hooks.rb:330 0.202
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.272
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.191
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.701
When I write some files expected to persist 2.473
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.576
And I take note of which tps features are available 0.546
And I shutdown Tails and wait for the computer to power off 5.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.884
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.017
Tags: @product
2:49.770
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.105
And I log in to a new session 20.630
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.573
And I plug USB drive "to_upgrade" 2.497
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.259
Then the running Tails is installed on USB drive "to_upgrade" 29.281
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.355
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.973
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.951
Then all tps features from the old Tails version are active 2.109
And Tails is running from USB drive "to_upgrade" 0.865
And the boot device has safe access rights 4.285
And the expected persistent files created with the old Tails version are present in the filesystem 1.614
And all persistent directories from the old Tails version have safe access rights 2.934
After features/support/hooks.rb:330 1.657
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:18.463
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 11.912
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.572
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.391
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.088
And Tor is ready 20.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.581
Given I shutdown Tails and wait for the computer to power off 6.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.314
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.489
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.126
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.380
# 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.368
When the network is plugged 0.084
And Tor is ready 20.018
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.081
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.954
Given I shutdown Tails and wait for the computer to power off 6.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.600
Then Tails is running version 6.3~testoverlayfs 0.062
And all tps features are active 2.740
And the file system changes introduced in version 6.3~testoverlayfs are present 0.621
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.076
And Tor is ready 22.613
Then the Upgrader considers the system as up-to-date 0.347
# 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 17.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.086
After features/support/hooks.rb:330 0.808
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
45.073
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 10.692
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.681
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.205
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.849
After features/support/hooks.rb:330 1.626
After features/support/hooks.rb:100 0.000