Project Number Date
test_Tails_ISO_stable 5076 06 Sep 2024, 08:37

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:14.580 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:22.375
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.334
When I start Tails from USB drive "old" with network unplugged 1:44.127
Then the boot device has safe access rights 4.407
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.795
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:28.673
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 32.696
And I take note of which tps features are available 1.566
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:326 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.454
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.067
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.377
When I write some files expected to persist 1.904
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.773
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.292
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.015
Tags: @product
2:34.931
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.244
And I log in to a new session 20.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.964
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.116
Then the running Tails is installed on USB drive "to_upgrade" 18.689
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.615
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.058
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.156
Then all tps features from the old Tails version are active 1.983
And Tails is running from USB drive "to_upgrade" 0.435
And the boot device has safe access rights 4.020
And the expected persistent files created with the old Tails version are present in the filesystem 1.645
And all persistent directories from the old Tails version have safe access rights 2.622
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.683
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.522
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
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.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.605
When the network is plugged 0.075
And Tor is ready 19.631
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.646
Given I shutdown Tails and wait for the computer to power off 16.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.969
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.423
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.240
When the network is plugged 0.070
And Tor is ready 17.263
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.616
Given I shutdown Tails and wait for the computer to power off 4.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.324
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.437
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.427
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.074
And Tor is ready 20.619
Then the Upgrader considers the system as up-to-date 0.349
# 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 15.056
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.538
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
59.280
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 10.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 1.166
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 45.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.656
After features/support/hooks.rb:326 0.989
After features/support/hooks.rb:100 0.000