Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 28 28 Aug 2024, 07:25

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:49.701 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:29.091
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.124
When I start Tails from USB drive "old" with network unplugged 1:53.009
Then the boot device has safe access rights 3.606
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 12.683
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.293
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:38.505
Then Tails is running from USB drive "old" 0.429
And I create a persistent partition 33.601
And I take note of which tps features are available 2.278
Then a Tails persistence partition exists on USB drive "old" 1.033
And I shutdown Tails and wait for the computer to power off 7.224
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.549
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.371
Then Tails is running from USB drive "old" 0.307
And all tps features are active 2.127
When I write some files expected to persist 1.937
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.523
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.506
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.451
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.492
And I log in to a new session 26.323
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.595
And I plug USB drive "to_upgrade" 2.447
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.196
Then the running Tails is installed on USB drive "to_upgrade" 19.963
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.596
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.289
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.594
Then all tps features from the old Tails version are active 2.107
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.624
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.838
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:16.813
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 13.528
And no SquashFS delta is installed 0.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
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.514
When the network is plugged 0.117
And Tor is ready 23.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.425
Given I shutdown Tails and wait for the computer to power off 11.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.952
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.893
And the file system changes introduced in version 6.2~testoverlayfs are present 0.439
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.448
# 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.304
When the network is plugged 0.092
And Tor is ready 20.637
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.963
Given I shutdown Tails and wait for the computer to power off 6.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.728
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.386
When the network is plugged 0.093
And Tor is ready 20.360
Then the Upgrader considers the system as up-to-date 0.413
# 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 16.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.174
After features/support/hooks.rb:326 1.457
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
37.212
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 12.266
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 17.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.482
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.000