Project Number Date
test_Tails_ISO_stable 5165 09 Oct 2024, 21:30

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:43.579 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:9.551
Before features/support/hooks.rb:269 0.007
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 33.115
When I start Tails from USB drive "old" with network unplugged 1:31.027
Then the boot device has safe access rights 3.123
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.323
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:34.006
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 31.886
And I take note of which tps features are available 1.492
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 8.447
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.220
Before features/support/hooks.rb:269 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.260
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.189
When I write some files expected to persist 2.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.619
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.924
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.483
Before features/support/hooks.rb:269 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.300
And I log in to a new session 19.689
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.648
Then the running Tails is installed on USB drive "to_upgrade" 24.169
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.538
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.585
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.492
Then all tps features from the old Tails version are active 1.617
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.956
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.573
After features/support/hooks.rb:326 1.015
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:47.445
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.510
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.169
And Tor is ready 27.578
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.372
Given I shutdown Tails and wait for the computer to power off 10.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.297
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.985
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.328
When the network is plugged 0.210
And Tor is ready 19.226
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.523
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.156
Given I shutdown Tails and wait for the computer to power off 57.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.511
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.382
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.071
And Tor is ready 47.657
Then the Upgrader considers the system as up-to-date 0.306
# 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.935
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.090
After features/support/hooks.rb:326 0.846
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
45.969
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.907
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 26.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.732
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.000