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

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:1.175 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:13.970
Before features/support/hooks.rb:269 0.009
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.120
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 31.078
When I start Tails from USB drive "old" with network unplugged 1:37.021
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.403
And I unplug USB drive "old" 0.280
After features/support/hooks.rb:326 3.864
After features/support/hooks.rb:100 0.012
Tags: @product
2:10.620
Before features/support/hooks.rb:269 0.008
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login 1:26.826
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.352
And I take note of which tps features are available 2.361
Then a Tails persistence partition exists on USB drive "old" 0.961
And I shutdown Tails and wait for the computer to power off 8.538
After features/support/hooks.rb:326 0.223
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.105
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.646
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.295
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.384
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.433
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.788
After features/support/hooks.rb:326 0.093
After features/support/hooks.rb:100 0.021
Tags: @product
2:38.963
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.579
And I log in to a new session 23.008
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.837
And I plug USB drive "to_upgrade" 2.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.419
Then the running Tails is installed on USB drive "to_upgrade" 23.969
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:326 3.656
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.996
Before features/support/hooks.rb:269 0.013
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.213
Then all tps features from the old Tails version are active 1.686
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.654
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.403
After features/support/hooks.rb:326 1.026
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:58.836
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.874
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.451
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.077
And Tor is ready 21.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.072
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.341
Given I shutdown Tails and wait for the computer to power off 9.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.891
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.481
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.298
When the network is plugged 0.072
And Tor is ready 19.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.307
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.005
Given I shutdown Tails and wait for the computer to power off 4.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.530
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.444
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.080
And Tor is ready 18.846
Then the Upgrader considers the system as up-to-date 10.892
# 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.531
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.894
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
36.683
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 11.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.994
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.403
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.509
After features/support/hooks.rb:326 0.873
After features/support/hooks.rb:100 0.000