Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 12 30 Jul 2024, 16: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:44.138 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:3.473
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.966
When I start Tails from USB drive "old" with network unplugged 1:28.163
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.332
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.311
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.553
After features/support/hooks.rb:100 0.016
Tags: @product
2:5.438
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login 1:19.965
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 33.400
And I take note of which tps features are available 1.637
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 9.045
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.983
Before features/support/hooks.rb:269 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.035
Then Tails is running from USB drive "old" 0.604
And all tps features are active 2.004
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.560
And all persistent directories from the old Tails version have safe access rights 2.975
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.032
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.355
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.424
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.227
And I log in to a new session 21.224
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.726
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.925
Then the running Tails is installed on USB drive "to_upgrade" 17.439
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 2.425
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.655
Before features/support/hooks.rb:269 0.005
Given a computer 0.308
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.462
Then all tps features from the old Tails version are active 1.814
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.557
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.515
After features/support/hooks.rb:326 1.067
After features/support/hooks.rb:100 0.010
6:16.539
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 10.297
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.034
And Tor is ready 18.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.590
Given I shutdown Tails and wait for the computer to power off 8.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.794
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.495
# 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.043
And Tor is ready 18.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.861
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.052
Given I shutdown Tails and wait for the computer to power off 4.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.022
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.899
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.042
And Tor is ready 17.671
Then the Upgrader considers the system as up-to-date 0.352
# 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.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.088
After features/support/hooks.rb:326 0.738
After features/support/hooks.rb:100 0.021
36.623
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 10.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.977
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 18.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000