Project Number Date
test_Tails_ISO_stable 4950 17 Jul 2024, 08:36

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:20.722 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:14.351
Before features/support/hooks.rb:269 0.013
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 33.749
When I start Tails from USB drive "old" with network unplugged 1:34.682
Then the boot device has safe access rights 3.411
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 7.225
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.285
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:30.777
Then Tails is running from USB drive "old" 0.422
And I create a persistent partition 34.721
And I take note of which tps features are available 1.659
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.013
Tags: @product
3:6.336
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.834
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.201
When I write some files expected to persist 2.001
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.394
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.603
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.011
Tags: @product
2:43.860
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 11.535
And I log in to a new session 21.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.364
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.296
Then the running Tails is installed on USB drive "to_upgrade" 26.431
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 2.238
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.041
Before features/support/hooks.rb:269 0.007
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.684
Then all tps features from the old Tails version are active 2.529
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.329
And the expected persistent files created with the old Tails version are present in the filesystem 1.472
And all persistent directories from the old Tails version have safe access rights 2.402
After features/support/hooks.rb:326 1.072
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:58.246
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 20.183
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.060
And Tor is ready 20.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.610
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.871
Given I shutdown Tails and wait for the computer to power off 8.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.864
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 6.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.290
When the network is plugged 0.034
And Tor is ready 18.334
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.835
Given I shutdown Tails and wait for the computer to power off 4.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.133
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.117
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.041
And Tor is ready 16.833
Then the Upgrader considers the system as up-to-date 10.975
# 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 14.893
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.820
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
40.598
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.755
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.498
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.828
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 21.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.080
After features/support/hooks.rb:326 1.052
After features/support/hooks.rb:100 0.000