Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 17 04 Aug 2024, 16:17

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:44.101 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:12.806
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.397
When I start Tails from USB drive "old" with network unplugged 1:36.041
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 8.621
After features/support/hooks.rb:100 0.025
Tags: @product
2:11.305
Before features/support/hooks.rb:269 0.014
Given a computer 0.282
And I start Tails from USB drive "old" with network unplugged and I login 1:27.487
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.162
And I take note of which tps features are available 1.704
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.494
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.012
Tags: @product
2:46.389
Before features/support/hooks.rb:269 0.008
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.930
Then Tails is running from USB drive "old" 0.759
And all tps features are active 2.338
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.950
And I take note of which tps features are available 0.570
And I shutdown Tails and wait for the computer to power off 4.639
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.507
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.721
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 21.490
And I log in to a new session 17.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.473
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.322
Then the running Tails is installed on USB drive "to_upgrade" 25.863
And I unplug USB drive "to_upgrade" 0.663
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 2.144
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.795
Before features/support/hooks.rb:269 0.024
Given a computer 0.343
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.084
Then all tps features from the old Tails version are active 1.770
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.361
And all persistent directories from the old Tails version have safe access rights 2.733
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.009
6:49.918
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 11.367
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.421
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.611
When the network is plugged 0.082
And Tor is ready 23.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.110
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.235
Given I shutdown Tails and wait for the computer to power off 8.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.180
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.251
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.450
# 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.263
When the network is plugged 0.037
And Tor is ready 21.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.756
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.558
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.618
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.077
And Tor is ready 20.188
Then the Upgrader considers the system as up-to-date 0.367
# 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.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.315
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.068
37.164
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 10.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.018
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 18.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.588
After features/support/hooks.rb:326 1.059
After features/support/hooks.rb:100 0.000