Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 71 19 Sep 2024, 16:48

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:26.267 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:11.063
Before features/support/hooks.rb:269 0.013
Given a computer 0.257
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.129
And I write an old version of the Tails USB image to disk "old" 32.406
When I start Tails from USB drive "old" with network unplugged 1:32.787
Then the boot device has safe access rights 3.429
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.818
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.773
Before features/support/hooks.rb:269 0.008
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:28.443
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.550
And I take note of which tps features are available 1.842
Then a Tails persistence partition exists on USB drive "old" 0.976
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.637
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.102
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.047
When I write some files expected to persist 1.893
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.585
And I take note of which tps features are available 0.353
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.030
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.453
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.500
And I log in to a new session 19.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.848
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.723
Then the running Tails is installed on USB drive "to_upgrade" 27.911
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.134
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.175
Before features/support/hooks.rb:269 0.006
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.360
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.607
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.137
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 13.253
And no SquashFS delta is installed 0.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.693
When the network is plugged 0.091
And Tor is ready 22.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.147
Given I shutdown Tails and wait for the computer to power off 10.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.517
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.464
# 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.278
When the network is plugged 0.062
And Tor is ready 18.260
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.821
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.640
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.074
And Tor is ready 20.924
Then the Upgrader considers the system as up-to-date 0.299
# 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 14.076
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.316
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.026
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.824
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.792
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 17.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.000
After features/support/hooks.rb:326 1.460
After features/support/hooks.rb:100 0.000