Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 62 03 Sep 2024, 23:59

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.075 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:19.566
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 34.193
When I start Tails from USB drive "old" with network unplugged 1:39.873
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.781
Before features/support/hooks.rb:269 0.003
Given a computer 0.522
And I start Tails from USB drive "old" with network unplugged and I login 1:24.143
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 33.880
And I take note of which tps features are available 2.154
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.835
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.849
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.297
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.865
When I write some files expected to persist 1.817
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.584
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.850
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.322
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 13.316
And I log in to a new session 21.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.812
Then the running Tails is installed on USB drive "to_upgrade" 24.860
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 1.186
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.213
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.484
Then all tps features from the old Tails version are active 2.834
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.946
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:54.028
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.756
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.573
When the network is plugged 0.094
And Tor is ready 19.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.745
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.629
Given I shutdown Tails and wait for the computer to power off 11.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.804
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.569
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.307
When the network is plugged 0.104
And Tor is ready 19.864
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.884
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.331
Given I shutdown Tails and wait for the computer to power off 4.833
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.561
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.119
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.353
When the network is plugged 0.095
And Tor is ready 17.865
Then the Upgrader considers the system as up-to-date 10.924
# 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 13.706
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.314
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.821
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 20.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.468
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000