Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 73 15 Oct 2024, 20:12

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:21.528 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.798
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.172
When I start Tails from USB drive "old" with network unplugged 1:36.684
Then the boot device has safe access rights 3.485
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 7.039
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.278
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 1:24.269
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 32.443
And I take note of which tps features are available 1.930
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 8.191
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.630
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.629
Then Tails is running from USB drive "old" 0.458
And all tps features are active 2.157
When I write some files expected to persist 1.668
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.559
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.595
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.104
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 11.745
And I log in to a new session 23.139
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.041
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.513
Then the running Tails is installed on USB drive "to_upgrade" 23.690
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.265
After features/support/hooks.rb:326 3.356
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.529
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.372
Then all tps features from the old Tails version are active 3.564
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.952
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.576
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:6.509
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.479
And no SquashFS delta is installed 0.198
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.081
And Tor is ready 23.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.044
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.535
Given I shutdown Tails and wait for the computer to power off 13.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.300
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.382
When the network is plugged 0.085
And Tor is ready 19.677
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.126
Given I shutdown Tails and wait for the computer to power off 4.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.615
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.465
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.101
And Tor is ready 20.015
Then the Upgrader considers the system as up-to-date 0.327
# 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.739
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.428
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.676
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 10.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.163
But a current signing key is available on our website 0.000
When the network is plugged 0.139
And Tor is ready 21.475
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.051
After features/support/hooks.rb:326 2.297
After features/support/hooks.rb:100 0.000