Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 58 28 Sep 2024, 07:17

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 19:28.556 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.273
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.078
And I write an old version of the Tails USB image to disk "old" 32.459
When I start Tails from USB drive "old" with network unplugged 1:33.055
Then the boot device has safe access rights 3.322
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:326 3.724
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.538
Before features/support/hooks.rb:269 0.007
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:22.891
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 32.034
And I take note of which tps features are available 1.599
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.542
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.152
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.925
Then Tails is running from USB drive "old" 1.056
And all tps features are active 2.146
When I write some files expected to persist 2.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.838
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.690
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 4.094
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.456
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.128
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.648
And I log in to a new session 21.216
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.115
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.287
Then the running Tails is installed on USB drive "to_upgrade" 23.951
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.934
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.820
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.915
Then all tps features from the old Tails version are active 2.650
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.815
And the expected persistent files created with the old Tails version are present in the filesystem 1.506
And all persistent directories from the old Tails version have safe access rights 2.360
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.513
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.025
And no SquashFS delta is installed 0.505
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.081
And Tor is ready 21.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.750
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.019
Given I shutdown Tails and wait for the computer to power off 11.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.000
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.258
When the network is plugged 0.073
And Tor is ready 17.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.676
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.628
Given I shutdown Tails and wait for the computer to power off 4.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.677
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.425
When the network is plugged 0.072
And Tor is ready 19.742
Then the Upgrader considers the system as up-to-date 0.326
# 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.394
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
37.129
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.875
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.543
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.762
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.733
After features/support/hooks.rb:326 0.669
After features/support/hooks.rb:100 0.000