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

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:14.209 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:13.106
Before features/support/hooks.rb:269 0.006
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 30.861
When I start Tails from USB drive "old" with network unplugged 1:36.066
Then the boot device has safe access rights 3.550
And Tails is running from USB drive "old" 0.462
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:326 3.521
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.315
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:30.537
Then Tails is running from USB drive "old" 0.470
And I create a persistent partition 32.910
And I take note of which tps features are available 1.525
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.807
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.118
Before features/support/hooks.rb:269 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.863
Then Tails is running from USB drive "old" 0.451
And all tps features are active 2.158
When I write some files expected to persist 1.900
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.496
And all persistent directories from the old Tails version have safe access rights 3.473
And I take note of which tps features are available 0.586
And I shutdown Tails and wait for the computer to power off 4.539
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.128
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.012
Tags: @product
2:47.249
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.880
And I log in to a new session 20.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.071
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.409
Then the running Tails is installed on USB drive "to_upgrade" 28.204
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.565
After features/support/hooks.rb:326 3.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.660
Before features/support/hooks.rb:269 0.007
Given a computer 0.279
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.203
Then all tps features from the old Tails version are active 2.130
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.722
And the expected persistent files created with the old Tails version are present in the filesystem 2.005
And all persistent directories from the old Tails version have safe access rights 2.947
After features/support/hooks.rb:326 1.402
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.399
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 13.934
And no SquashFS delta is installed 0.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.609
When the network is plugged 0.078
And Tor is ready 21.674
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.395
Given I shutdown Tails and wait for the computer to power off 11.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.845
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.291
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.324
When the network is plugged 0.075
And Tor is ready 21.006
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.963
Given I shutdown Tails and wait for the computer to power off 6.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.923
Then Tails is running version 6.3~testoverlayfs 0.039
And all tps features are active 2.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.106
And Tor is ready 21.907
Then the Upgrader considers the system as up-to-date 0.355
# 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 17.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.587
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.359
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.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.970
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.408
After features/support/hooks.rb:326 0.738
After features/support/hooks.rb:100 0.000