Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 18 05 Aug 2024, 17: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 20:28.933 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:30.749
Before features/support/hooks.rb:269 0.005
Given a computer 0.906
And I create a 7200 MiB disk named "old" 0.344
And I plug USB drive "old" 1.088
And I write an old version of the Tails USB image to disk "old" 32.552
When I start Tails from USB drive "old" with network unplugged 1:51.660
Then the boot device has safe access rights 3.177
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 7.985
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.170
Before features/support/hooks.rb:269 0.006
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:26.667
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 36.047
And I take note of which tps features are available 2.244
Then a Tails persistence partition exists on USB drive "old" 0.961
And I shutdown Tails and wait for the computer to power off 6.588
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.697
Before features/support/hooks.rb:269 0.008
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.199
Then Tails is running from USB drive "old" 0.380
And all tps features are active 3.252
When I write some files expected to persist 1.907
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.449
And I take note of which tps features are available 0.653
And I shutdown Tails and wait for the computer to power off 5.116
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.795
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.211
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.250
And I log in to a new session 19.917
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.301
Then the running Tails is installed on USB drive "to_upgrade" 23.192
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 7.213
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.910
Before features/support/hooks.rb:269 0.007
Given a computer 0.255
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.684
Then all tps features from the old Tails version are active 1.796
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.658
And the expected persistent files created with the old Tails version are present in the filesystem 1.611
And all persistent directories from the old Tails version have safe access rights 2.551
After features/support/hooks.rb:326 1.025
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:49.945
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 13.458
And no SquashFS delta is installed 0.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.034
And Tor is ready 25.094
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.914
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.865
Given I shutdown Tails and wait for the computer to power off 8.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.930
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.436
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.274
When the network is plugged 0.052
And Tor is ready 20.885
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 8.587
Given I shutdown Tails and wait for the computer to power off 6.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.381
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.334
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.055
And Tor is ready 20.760
Then the Upgrader considers the system as up-to-date 0.347
# 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.162
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
45.247
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.033
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 23.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.654
After features/support/hooks.rb:326 0.877
After features/support/hooks.rb:100 0.000