Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 20 14 Dec 2024, 00:43

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 21:14.582 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:1.176
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.097
When I start Tails from USB drive "old" with network unplugged 1:25.063
Then the boot device has safe access rights 3.529
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.168
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.817
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.683
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:28.363
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.430
And I take note of which tps features are available 1.851
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.224
Before features/support/hooks.rb:269 0.004
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.959
Then Tails is running from USB drive "old" 0.669
And all tps features are active 2.555
When I write some files expected to persist 2.572
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.865
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.700
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.013
Tags: @product
2:42.420
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.865
And I log in to a new session 21.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.029
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.241
Then the running Tails is installed on USB drive "to_upgrade" 24.753
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.298
After features/support/hooks.rb:326 7.057
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.334
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.396
Then all tps features from the old Tails version are active 3.779
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:326 1.163
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:55.351
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 34.319
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.613
And Tor is ready 23.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.450
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.581
Given I shutdown Tails and wait for the computer to power off 8.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.299
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.648
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.367
When the network is plugged 0.091
And Tor is ready 20.074
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.646
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.347
Given I shutdown Tails and wait for the computer to power off 4.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.679
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.108
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.065
And Tor is ready 47.889
Then the Upgrader considers the system as up-to-date 0.295
# 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.529
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.081
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.391
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.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.894
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 20.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.431
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.000