Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 23 23 Aug 2024, 07: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:58.249 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:15.018
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.775
When I start Tails from USB drive "old" with network unplugged 1:40.716
Then the boot device has safe access rights 3.184
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.040
Tags: @product
2:6.134
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:23.439
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 31.315
And I take note of which tps features are available 1.595
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.405
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.979
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.791
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.949
When I write some files expected to persist 1.713
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.100
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.022
Tags: @product
2:34.878
Before features/support/hooks.rb:269 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.179
And I log in to a new session 20.822
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.516
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.964
Then the running Tails is installed on USB drive "to_upgrade" 23.432
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:326 2.183
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.441
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.421
Then all tps features from the old Tails version are active 1.684
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.097
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.421
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:13.500
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.687
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.108
And Tor is ready 18.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.548
Given I shutdown Tails and wait for the computer to power off 10.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.687
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.291
When the network is plugged 0.093
And Tor is ready 19.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.189
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.628
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.704
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.064
And Tor is ready 18.978
Then the Upgrader considers the system as up-to-date 0.329
# 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 14.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.086
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.295
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
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.715
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 16.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.000