Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 20 20 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 19:33.887 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:16.179
Before features/support/hooks.rb:269 0.006
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.329
When I start Tails from USB drive "old" with network unplugged 1:40.497
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.672
After features/support/hooks.rb:100 0.014
Tags: @product
2:3.268
Before features/support/hooks.rb:269 0.009
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:19.908
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.992
And I take note of which tps features are available 1.502
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.402
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.014
Tags: @product
2:53.552
Before features/support/hooks.rb:269 0.010
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.847
Then Tails is running from USB drive "old" 0.430
And all tps features are active 2.084
When I write some files expected to persist 1.790
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.620
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.506
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.935
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.818
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.337
And I log in to a new session 27.881
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.520
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.117
Then the running Tails is installed on USB drive "to_upgrade" 21.954
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:326 2.407
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.925
Before features/support/hooks.rb:269 0.007
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.069
Then all tps features from the old Tails version are active 2.720
And Tails is running from USB drive "to_upgrade" 0.416
And the boot device has safe access rights 4.008
And the expected persistent files created with the old Tails version are present in the filesystem 1.737
And all persistent directories from the old Tails version have safe access rights 2.740
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:28.315
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 15.703
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.084
And Tor is ready 21.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.953
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.100
Given I shutdown Tails and wait for the computer to power off 8.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.619
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.306
When the network is plugged 0.075
And Tor is ready 20.669
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.200
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.315
Given I shutdown Tails and wait for the computer to power off 4.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.670
Then Tails is running version 6.3~testoverlayfs 0.046
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.085
And Tor is ready 19.167
Then the Upgrader considers the system as up-to-date 0.315
# 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.012
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.987
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
38.826
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.838
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 1.551
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 19.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000