Project Number Date
test_Tails_ISO_test-suite-options 4 19 Jun 2025, 21:16

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 26:41.147 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:47.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.521
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 41.111
When I start Tails from USB drive "old" with network unplugged 1:59.603
Then the boot device has safe access rights 3.829
And Tails is running from USB drive "old" 0.456
And there is no persistence partition on USB drive "old" 0.141
And process "udev-watchdog" is running 0.142
And udev-watchdog is monitoring the correct device 0.423
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 5.684
After features/support/hooks.rb:100 0.182
Tags: @product
2:54.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.199
Given a computer 0.872
And I start Tails from USB drive "old" with network unplugged and I login 1:53.262
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 46.967
And I take note of which tps features are available 2.932
Then a Tails persistence partition exists on USB drive "old" 1.011
And I shutdown Tails and wait for the computer to power off 8.902
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.010
Tags: @product
4:10.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.306
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:8.700
Then Tails is running from USB drive "old" 1.367
And all tps features are active 2.334
When I write some files expected to persist 2.000
# 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.623
And all persistent directories from the old Tails version have safe access rights 3.602
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 8.988
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.705
After features/support/hooks.rb:330 0.308
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.882
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 12.465
And I log in to a new session 30.931
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.635
And I plug USB drive "to_upgrade" 2.566
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.962
Then the running Tails is installed on USB drive "to_upgrade" 38.632
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.396
After features/support/hooks.rb:330 4.231
After features/support/hooks.rb:100 0.000
Tags: @product
3:15.371
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:56.928
Then all tps features from the old Tails version are active 2.431
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 4.040
And the expected persistent files created with the old Tails version are present in the filesystem 2.115
And all persistent directories from the old Tails version have safe access rights 9.182
After features/support/hooks.rb:330 2.382
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:24.059
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 32.653
And no SquashFS delta is installed 2.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.733
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.180
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.695
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.898
When the network is plugged 0.078
And Tor is ready 25.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.973
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.089
Given I shutdown Tails and wait for the computer to power off 14.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.881
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.415
When the network is plugged 0.078
And Tor is ready 28.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.216
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.347
Given I shutdown Tails and wait for the computer to power off 6.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.365
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 6.224
And the file system changes introduced in version 6.3~testoverlayfs are present 1.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.140
# 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.647
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.515
When the network is plugged 0.233
And Tor is ready 22.743
Then the Upgrader considers the system as up-to-date 0.363
# 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 20.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.990
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
51.566
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.339
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 23.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.341
After features/support/hooks.rb:330 2.105
After features/support/hooks.rb:100 0.000