Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 65 05 Sep 2024, 16:56

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 22:10.000 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
3:11.256
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 1:21.579
When I start Tails from USB drive "old" with network unplugged 1:43.760
Then the boot device has safe access rights 3.468
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 3.771
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.144
Before features/support/hooks.rb:269 0.007
Given a computer 0.315
And I start Tails from USB drive "old" with network unplugged and I login 1:29.208
Then Tails is running from USB drive "old" 0.432
And I create a persistent partition 32.988
And I take note of which tps features are available 2.052
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 9.308
After features/support/hooks.rb:326 0.228
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.198
Before features/support/hooks.rb:269 0.004
Given a computer 0.358
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.196
Then Tails is running from USB drive "old" 0.410
And all tps features are active 2.414
When I write some files expected to persist 2.280
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.629
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 4.321
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.337
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.934
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.190
And I log in to a new session 24.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.080
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.414
Then the running Tails is installed on USB drive "to_upgrade" 25.206
And I unplug USB drive "to_upgrade" 0.354
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.845
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.134
Before features/support/hooks.rb:269 0.025
Given a computer 0.843
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.799
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.864
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.747
After features/support/hooks.rb:326 0.889
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:38.641
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 37.160
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.120
And Tor is ready 24.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.016
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.948
Given I shutdown Tails and wait for the computer to power off 11.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.218
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 7.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
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.416
# 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.290
When the network is plugged 0.732
And Tor is ready 19.499
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.813
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.464
Given I shutdown Tails and wait for the computer to power off 6.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.978
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.467
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.393
And Tor is ready 17.592
Then the Upgrader considers the system as up-to-date 0.354
# 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 0.971
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
42.692
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.367
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 1.026
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.770
After features/support/hooks.rb:326 0.889
After features/support/hooks.rb:100 0.000