Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 77 19 Oct 2024, 07:36

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:37.695 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:20.912
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 35.719
When I start Tails from USB drive "old" with network unplugged 1:38.650
Then the boot device has safe access rights 3.758
And Tails is running from USB drive "old" 0.476
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.487
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.066
Before features/support/hooks.rb:269 0.008
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login 1:32.269
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 30.072
And I take note of which tps features are available 1.611
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.535
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.013
Tags: @product
3:1.288
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.125
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.449
When I write some files expected to persist 1.833
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.533
And all persistent directories from the old Tails version have safe access rights 2.589
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.386
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.020
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.429
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 15.291
And I log in to a new session 19.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.726
Then the running Tails is installed on USB drive "to_upgrade" 21.953
And I unplug USB drive "to_upgrade" 0.296
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 3.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.351
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.134
Then all tps features from the old Tails version are active 2.168
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 4.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.671
And all persistent directories from the old Tails version have safe access rights 3.006
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:59.338
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 16.146
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.069
And Tor is ready 51.966
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.245
Given I shutdown Tails and wait for the computer to power off 11.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.047
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.366
When the network is plugged 0.097
And Tor is ready 19.396
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.166
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.670
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.431
When the network is plugged 0.106
And Tor is ready 20.239
Then the Upgrader considers the system as up-to-date 0.335
# 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.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.030
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:1.308
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 9.554
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.857
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.863
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 49.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.700
After features/support/hooks.rb:326 1.131
After features/support/hooks.rb:100 0.000