Project Number Date
test_Tails_ISO_devel 3491 24 Aug 2024, 12:33

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 19:3.710 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:2.342
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 28.387
When I start Tails from USB drive "old" with network unplugged 1:28.397
Then the boot device has safe access rights 3.119
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.311
After features/support/hooks.rb:326 3.534
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.582
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:23.420
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.831
And I take note of which tps features are available 1.414
Then a Tails persistence partition exists on USB drive "old" 1.049
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.871
Before features/support/hooks.rb:269 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.664
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.330
When I write some files expected to persist 1.620
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.294
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.548
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.686
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.267
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.002
And I log in to a new session 18.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.421
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.373
Then the running Tails is installed on USB drive "to_upgrade" 19.423
And I unplug USB drive "to_upgrade" 0.276
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 7.679
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.007
Before features/support/hooks.rb:269 0.009
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.116
Then all tps features from the old Tails version are active 2.672
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 4.607
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.478
After features/support/hooks.rb:326 1.212
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
6:38.905
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.409
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.076
And Tor is ready 19.475
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.704
Given I shutdown Tails and wait for the computer to power off 8.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.408
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.345
When the network is plugged 0.077
And Tor is ready 19.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.720
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.294
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.240
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.086
And Tor is ready 18.371
Then the Upgrader considers the system as up-to-date 10.708
# 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 13.998
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.915
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.733
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.696
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.717
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.526
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.000