Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 23 17 Dec 2024, 00:28

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:9.223 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:20.883
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.174
When I start Tails from USB drive "old" with network unplugged 1:44.173
Then the boot device has safe access rights 3.233
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 7.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.509
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:26.983
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 32.008
And I take note of which tps features are available 1.450
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.657
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.636
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.514
Then Tails is running from USB drive "old" 0.572
And all tps features are active 2.183
When I write some files expected to persist 2.416
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.920
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.981
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.070
And I log in to a new session 19.892
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.099
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.171
Then the running Tails is installed on USB drive "to_upgrade" 24.889
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.112
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.912
Before features/support/hooks.rb:269 0.007
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.897
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.446
And the boot device has safe access rights 3.579
And the expected persistent files created with the old Tails version are present in the filesystem 1.539
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:58.740
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 12.008
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.550
When the network is plugged 0.067
And Tor is ready 50.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.940
Given I shutdown Tails and wait for the computer to power off 8.737
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.041
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.440
# 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.327
When the network is plugged 0.071
And Tor is ready 18.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.332
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.555
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.649
And the file system changes introduced in version 6.3~testoverlayfs are present 0.615
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.301
When the network is plugged 0.065
And Tor is ready 21.846
Then the Upgrader considers the system as up-to-date 0.348
# 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 16.058
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.063
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
58.561
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 9.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.712
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.801
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 46.475
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.000