Project Number Date
test_Tails_ISO_20522-ocr-more 4 14 Dec 2024, 05:23

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 18:44.593 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:0.824
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.639
When I start Tails from USB drive "old" with network unplugged 1:27.058
Then the boot device has safe access rights 2.901
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 7.112
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.855
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:23.071
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 32.741
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 8.337
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.815
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.648
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.887
When I write some files expected to persist 2.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.486
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.228
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.731
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.726
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.694
And I log in to a new session 21.337
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.543
And I plug USB drive "to_upgrade" 4.555
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.325
Then the running Tails is installed on USB drive "to_upgrade" 21.861
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.824
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.564
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.769
Then all tps features from the old Tails version are active 1.792
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.322
And the expected persistent files created with the old Tails version are present in the filesystem 1.563
And all persistent directories from the old Tails version have safe access rights 2.598
After features/support/hooks.rb:326 0.890
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:23.234
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.285
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.073
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.985
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.488
Given I shutdown Tails and wait for the computer to power off 12.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.160
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.114
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.500
When the network is plugged 0.074
And Tor is ready 15.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.671
Given I shutdown Tails and wait for the computer to power off 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.536
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.076
And Tor is ready 21.030
Then the Upgrader considers the system as up-to-date 0.281
# 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.443
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.263
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.573
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.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.891
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.482
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000