Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 9 08 Aug 2024, 07:13

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:56.689 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:27.636
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.986
When I start Tails from USB drive "old" with network unplugged 1:50.922
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.549
Before features/support/hooks.rb:269 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:26.236
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.473
And I take note of which tps features are available 1.827
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 10.571
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.011
Before features/support/hooks.rb:269 0.004
Given a computer 0.523
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.118
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.965
When I write some files expected to persist 1.653
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
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.646
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.174
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.694
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.345
And I log in to a new session 17.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.263
And I plug USB drive "to_upgrade" 2.368
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.858
Then the running Tails is installed on USB drive "to_upgrade" 16.633
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 6.937
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.688
Before features/support/hooks.rb:269 0.007
Given a computer 0.316
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.260
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 3.314
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:18.213
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 11.832
And no SquashFS delta is installed 0.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.069
And Tor is ready 20.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.518
Given I shutdown Tails and wait for the computer to power off 15.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.108
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.307
When the network is plugged 0.071
And Tor is ready 19.001
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.984
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.721
Given I shutdown Tails and wait for the computer to power off 4.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.555
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.069
And Tor is ready 18.292
Then the Upgrader considers the system as up-to-date 0.350
# 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.028
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.024
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
36.895
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.875
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.785
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 18.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.657
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.000