Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 70 08 Oct 2024, 07:40

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:2.848 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:12.125
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.689
When I start Tails from USB drive "old" with network unplugged 1:36.829
Then the boot device has safe access rights 3.299
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.637
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.362
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:27.755
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 31.133
And I take note of which tps features are available 2.055
Then a Tails persistence partition exists on USB drive "old" 0.911
And I shutdown Tails and wait for the computer to power off 8.906
After features/support/hooks.rb:326 0.247
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.819
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.735
Then Tails is running from USB drive "old" 0.423
And all tps features are active 2.300
When I write some files expected to persist 2.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.356
And all persistence configuration files have safe access rights 0.496
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 4.246
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.917
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.182
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.287
And I log in to a new session 19.485
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.568
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.288
Then the running Tails is installed on USB drive "to_upgrade" 22.225
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 3.290
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.644
Before features/support/hooks.rb:269 0.007
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.790
Then all tps features from the old Tails version are active 1.701
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:17.758
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 13.370
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.575
When the network is plugged 0.074
And Tor is ready 28.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.011
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.594
Given I shutdown Tails and wait for the computer to power off 13.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.908
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.812
And the file system changes introduced in version 6.2~testoverlayfs are present 0.495
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.315
When the network is plugged 0.376
And Tor is ready 22.369
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.603
Given I shutdown Tails and wait for the computer to power off 6.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.741
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.457
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.070
And Tor is ready 19.254
Then the Upgrader considers the system as up-to-date 10.889
# 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.301
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 0.772
After features/support/hooks.rb:100 0.052
Tags: @product @automatic_upgrade
36.956
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.370
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.473
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.000