Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 21 08 Aug 2024, 17:58

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 18:50.404 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:9.018
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.342
When I start Tails from USB drive "old" with network unplugged 1:33.318
Then the boot device has safe access rights 3.105
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.548
After features/support/hooks.rb:100 0.026
Tags: @product
2:10.919
Before features/support/hooks.rb:269 0.005
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:29.289
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.495
And I take note of which tps features are available 1.507
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.248
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.241
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.551
Then Tails is running from USB drive "old" 0.330
And all tps features are active 1.946
When I write some files expected to persist 1.790
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.358
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.370
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.724
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.976
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.497
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 11.031
And I log in to a new session 21.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.003
Then the running Tails is installed on USB drive "to_upgrade" 17.814
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.038
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.353
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.000
Then all tps features from the old Tails version are active 1.659
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:326 1.012
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:14.949
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 11.508
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
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.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.073
And Tor is ready 20.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.601
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.255
Given I shutdown Tails and wait for the computer to power off 8.930
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.638
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.367
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.253
When the network is plugged 0.084
And Tor is ready 17.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.730
Given I shutdown Tails and wait for the computer to power off 6.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.927
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.060
And Tor is ready 19.752
Then the Upgrader considers the system as up-to-date 0.312
# 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.391
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.162
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.425
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 9.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.088
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.000