Project Number Date
test_Tails_ISO_20522-ocr-more 12 21 Dec 2024, 05:21

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:9.726 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.530
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.457
When I start Tails from USB drive "old" with network unplugged 1:37.741
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 6.948
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.946
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:30.317
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 32.303
And I take note of which tps features are available 1.709
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.810
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.834
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.276
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 3.106
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.258
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.783
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.419
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.510
And I log in to a new session 20.161
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.598
And I plug USB drive "to_upgrade" 3.727
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.964
Then the running Tails is installed on USB drive "to_upgrade" 22.012
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.483
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.400
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.719
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.505
And the expected persistent files created with the old Tails version are present in the filesystem 1.436
And all persistent directories from the old Tails version have safe access rights 2.352
After features/support/hooks.rb:326 1.123
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.853
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 12.778
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.508
When the network is plugged 0.068
And Tor is ready 20.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.651
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.643
Given I shutdown Tails and wait for the computer to power off 18.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.071
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.263
When the network is plugged 0.082
And Tor is ready 16.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.830
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.267
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.349
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.572
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.525
When the network is plugged 0.071
And Tor is ready 17.097
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 16.282
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.766
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 15.349
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 17.422
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.423
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.000