Project Number Date
test_Tails_ISO_20522-ocr-more 11 20 Dec 2024, 05:27

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:36.746 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:7.961
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 27.608
When I start Tails from USB drive "old" with network unplugged 1:35.072
Then the boot device has safe access rights 3.003
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.447
After features/support/hooks.rb:100 0.029
Tags: @product
2:6.428
Before features/support/hooks.rb:269 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:24.274
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.467
And I take note of which tps features are available 2.025
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.352
After features/support/hooks.rb:326 0.220
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.382
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.224
Then Tails is running from USB drive "old" 0.364
And all tps features are active 1.931
When I write some files expected to persist 1.939
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
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.385
And I take note of which tps features are available 0.664
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.705
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.858
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.145
And I log in to a new session 25.538
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.813
And I plug USB drive "to_upgrade" 4.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.593
Then the running Tails is installed on USB drive "to_upgrade" 20.923
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 2.723
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.458
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.424
Then all tps features from the old Tails version are active 2.274
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.283
And the expected persistent files created with the old Tails version are present in the filesystem 1.573
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:326 1.718
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
6:24.162
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.449
And no SquashFS delta is installed 0.394
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.075
And Tor is ready 19.669
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.685
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.154
Given I shutdown Tails and wait for the computer to power off 8.882
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.697
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.874
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.408
When the network is plugged 0.106
And Tor is ready 19.012
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.547
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.552
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.132
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.069
And Tor is ready 18.134
Then the Upgrader considers the system as up-to-date 0.372
# 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 17.445
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.001
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
48.496
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 23.928
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 18.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.497
After features/support/hooks.rb:326 0.914
After features/support/hooks.rb:100 0.000