Project Number Date
test_Tails_ISO_20522-ocr-more 17 26 Dec 2024, 05:20

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:51.012 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.683
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.919
When I start Tails from USB drive "old" with network unplugged 1:33.388
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.129
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 7.106
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.648
Before features/support/hooks.rb:269 0.011
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:33.399
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 32.165
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 8.273
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.974
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.626
Then Tails is running from USB drive "old" 1.235
And all tps features are active 2.042
When I write some files expected to persist 1.600
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 3.922
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.948
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.830
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.494
And I log in to a new session 21.183
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.565
And I plug USB drive "to_upgrade" 3.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.909
Then the running Tails is installed on USB drive "to_upgrade" 21.016
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 3.018
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.924
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.029
Then all tps features from the old Tails version are active 1.831
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.504
And all persistent directories from the old Tails version have safe access rights 2.643
After features/support/hooks.rb:326 1.086
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:24.175
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.256
And no SquashFS delta is installed 0.298
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.486
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.083
And Tor is ready 24.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.495
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.639
Given I shutdown Tails and wait for the computer to power off 10.737
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.009
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.644
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.393
When the network is plugged 0.072
And Tor is ready 16.927
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.042
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.775
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.572
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.475
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.093
And Tor is ready 15.790
Then the Upgrader considers the system as up-to-date 10.867
# 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.927
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.189
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.775
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 9.808
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.542
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 18.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.616
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.000