Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 4 02 Oct 2024, 01:10

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:54.745 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:1.454
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.026
When I start Tails from USB drive "old" with network unplugged 1:28.233
Then the boot device has safe access rights 2.956
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 6.976
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.871
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:19.954
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 30.626
And I take note of which tps features are available 1.622
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.343
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.718
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.939
Then Tails is running from USB drive "old" 0.419
And all tps features are active 1.889
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.282
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.248
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.853
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.622
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.619
And I log in to a new session 18.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.512
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.487
Then the running Tails is installed on USB drive "to_upgrade" 16.279
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.431
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.319
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.276
Then all tps features from the old Tails version are active 1.579
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 3.176
And the expected persistent files created with the old Tails version are present in the filesystem 1.425
And all persistent directories from the old Tails version have safe access rights 2.393
After features/support/hooks.rb:326 0.919
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:46.591
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 11.514
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
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.441
When the network is plugged 0.072
And Tor is ready 21.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.421
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.317
Given I shutdown Tails and wait for the computer to power off 8.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.603
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.175
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
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.289
# 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.321
When the network is plugged 0.094
And Tor is ready 22.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.244
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.296
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.159
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.077
And Tor is ready 32.630
Then the Upgrader considers the system as up-to-date 0.308
# 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 13.312
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.095
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.166
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.948
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.806
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 20.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.979
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.000