Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 11 10 Aug 2024, 07:50

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:8.948 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:26.719
Before features/support/hooks.rb:269 0.007
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.314
When I start Tails from USB drive "old" with network unplugged 1:49.440
Then the boot device has safe access rights 3.460
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 8.577
After features/support/hooks.rb:100 0.013
Tags: @product
2:11.270
Before features/support/hooks.rb:269 0.008
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:23.875
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 33.575
And I take note of which tps features are available 2.535
Then a Tails persistence partition exists on USB drive "old" 1.827
And I shutdown Tails and wait for the computer to power off 8.794
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.011
Tags: @product
3:10.575
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.634
Then Tails is running from USB drive "old" 0.468
And all tps features are active 2.074
When I write some files expected to persist 1.740
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.499
And I take note of which tps features are available 0.702
And I shutdown Tails and wait for the computer to power off 4.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.148
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.836
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.691
And I log in to a new session 21.664
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.543
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.130
Then the running Tails is installed on USB drive "to_upgrade" 25.894
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.026
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.675
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.233
Then all tps features from the old Tails version are active 2.530
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.275
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:41.654
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 13.650
And no SquashFS delta is installed 0.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.095
And Tor is ready 19.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.926
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.915
Given I shutdown Tails and wait for the computer to power off 11.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.780
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.125
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.420
# 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.286
When the network is plugged 0.094
And Tor is ready 21.061
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.489
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.024
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.941
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 2.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.090
And Tor is ready 18.067
Then the Upgrader considers the system as up-to-date 0.365
# 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.449
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.028
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.216
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
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 0.886
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.065
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.000