Project Number Date
test_Tails_ISO_20522-ocr-more 3 13 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:18.895 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:2.853
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.368
When I start Tails from USB drive "old" with network unplugged 1:28.227
Then the boot device has safe access rights 2.952
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 0.958
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.589
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:29.307
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 34.000
And I take note of which tps features are available 1.660
Then a Tails persistence partition exists on USB drive "old" 0.750
And I shutdown Tails and wait for the computer to power off 10.336
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.947
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.492
Then Tails is running from USB drive "old" 0.641
And all tps features are active 1.963
When I write some files expected to persist 2.132
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.449
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.697
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.546
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 10.256
And I log in to a new session 19.666
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.679
And I plug USB drive "to_upgrade" 3.700
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.518
Then the running Tails is installed on USB drive "to_upgrade" 21.315
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 7.176
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.562
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.206
Then all tps features from the old Tails version are active 1.821
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.191
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.429
After features/support/hooks.rb:326 0.952
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:58.963
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 12.922
And no SquashFS delta is installed 0.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.355
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.096
And Tor is ready 20.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.540
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.888
Given I shutdown Tails and wait for the computer to power off 12.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.161
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.543
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# 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.358
When the network is plugged 0.078
And Tor is ready 16.741
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.470
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.941
Given I shutdown Tails and wait for the computer to power off 6.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.638
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.305
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.079
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.499
When the network is plugged 0.083
And Tor is ready 46.592
Then the Upgrader considers the system as up-to-date 0.289
# 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.266
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.053
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.431
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 10.271
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.978
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 18.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.889
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.000