Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 51 23 Sep 2024, 07:31

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 20:10.393 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.054
Before features/support/hooks.rb:269 0.010
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 32.320
When I start Tails from USB drive "old" with network unplugged 1:28.803
Then the boot device has safe access rights 3.484
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:326 3.643
After features/support/hooks.rb:100 0.011
Tags: @product
2:24.433
Before features/support/hooks.rb:269 0.009
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:38.092
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 32.881
And I take note of which tps features are available 2.463
Then a Tails persistence partition exists on USB drive "old" 1.063
And I shutdown Tails and wait for the computer to power off 9.302
After features/support/hooks.rb:326 0.227
After features/support/hooks.rb:100 0.013
Tags: @product
3:3.087
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.375
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.813
When I write some files expected to persist 2.150
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.375
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 2.543
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.940
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.012
Tags: @product
2:34.582
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.256
And I log in to a new session 22.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.755
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.226
Then the running Tails is installed on USB drive "to_upgrade" 19.210
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 3.053
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.138
Before features/support/hooks.rb:269 0.008
Given a computer 0.296
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.882
Then all tps features from the old Tails version are active 2.261
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.955
And the expected persistent files created with the old Tails version are present in the filesystem 1.643
And all persistent directories from the old Tails version have safe access rights 2.767
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:0.154
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.468
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.070
And Tor is ready 19.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.859
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.989
Given I shutdown Tails and wait for the computer to power off 10.844
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.112
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.277
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.270
When the network is plugged 0.069
And Tor is ready 47.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.858
Given I shutdown Tails and wait for the computer to power off 4.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.250
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.902
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.066
And Tor is ready 19.026
Then the Upgrader considers the system as up-to-date 0.297
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.137
After features/support/hooks.rb:326 0.838
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.942
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.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.886
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 18.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.949
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.000