Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 1 01 Aug 2024, 22:58

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 19:38.153 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:23.221
Before features/support/hooks.rb:269 0.008
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.350
When I start Tails from USB drive "old" with network unplugged 1:47.387
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.734
After features/support/hooks.rb:100 0.013
Tags: @product
2:17.133
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:32.807
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.633
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.366
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.792
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.301
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.294
When I write some files expected to persist 1.893
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.850
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.569
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.119
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.015
Tags: @product
2:27.734
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 11.593
And I log in to a new session 18.484
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.612
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.455
Then the running Tails is installed on USB drive "to_upgrade" 18.663
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 3.383
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.301
Before features/support/hooks.rb:269 0.008
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.739
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 3.862
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.767
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:32.382
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 11.485
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.508
When the network is plugged 0.038
And Tor is ready 21.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.126
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.615
Given I shutdown Tails and wait for the computer to power off 11.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.278
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
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.310
# 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.047
And Tor is ready 18.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.598
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.503
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.656
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.418
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.417
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.040
And Tor is ready 20.202
Then the Upgrader considers the system as up-to-date 0.372
# 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.432
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.043
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
34.586
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 10.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.753
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 17.186
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.701
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.000