Project Number Date
test_Tails_ISO_20522-ocr-more 19 28 Dec 2024, 05: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 19:18.350 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:6.298
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.651
When I start Tails from USB drive "old" with network unplugged 1:31.277
Then the boot device has safe access rights 3.090
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.699
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.150
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:24.456
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 30.387
And I take note of which tps features are available 1.794
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.173
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.305
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:17.081
Then Tails is running from USB drive "old" 0.459
And all tps features are active 2.219
When I write some files expected to persist 1.741
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.424
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.520
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.144
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 10.900
And I log in to a new session 21.858
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.850
And I plug USB drive "to_upgrade" 3.750
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.152
Then the running Tails is installed on USB drive "to_upgrade" 18.181
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.370
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.031
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.998
Then all tps features from the old Tails version are active 1.639
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.537
And the expected persistent files created with the old Tails version are present in the filesystem 1.657
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:57.334
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 12.173
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.175
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.085
And Tor is ready 23.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.252
Given I shutdown Tails and wait for the computer to power off 8.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.253
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.319
When the network is plugged 0.089
And Tor is ready 44.603
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.799
Given I shutdown Tails and wait for the computer to power off 4.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.847
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.618
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.077
And Tor is ready 44.738
Then the Upgrader considers the system as up-to-date 0.359
# 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.697
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.287
After features/support/hooks.rb:326 0.811
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.084
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 10.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.957
After features/support/hooks.rb:326 0.861
After features/support/hooks.rb:100 0.000