Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 56 26 Sep 2024, 14:33

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:5.139 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:11.141
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.120
When I start Tails from USB drive "old" with network unplugged 1:34.344
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.025
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.195
Before features/support/hooks.rb:269 0.006
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:25.686
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 32.715
And I take note of which tps features are available 1.651
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.689
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.183
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.696
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.156
When I write some files expected to persist 2.575
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.531
And all persistent directories from the old Tails version have safe access rights 3.058
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.645
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.011
Tags: @product
2:44.906
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.859
And I log in to a new session 21.867
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.686
And I plug USB drive "to_upgrade" 2.536
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.480
Then the running Tails is installed on USB drive "to_upgrade" 25.011
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 2.004
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.453
Before features/support/hooks.rb:269 0.008
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.231
Then all tps features from the old Tails version are active 1.837
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.891
And the expected persistent files created with the old Tails version are present in the filesystem 1.728
And all persistent directories from the old Tails version have safe access rights 3.144
After features/support/hooks.rb:326 1.109
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:55.010
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.889
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.546
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.143
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.128
And Tor is ready 21.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.094
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.960
Given I shutdown Tails and wait for the computer to power off 11.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.233
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.968
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.341
When the network is plugged 0.074
And Tor is ready 21.719
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.461
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.938
Given I shutdown Tails and wait for the computer to power off 6.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.528
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.435
When the network is plugged 0.123
And Tor is ready 17.878
Then the Upgrader considers the system as up-to-date 0.321
# 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.912
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.102
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.063
Tags: @product @automatic_upgrade
37.249
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.896
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.293
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.720
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.700
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000