Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 29 20 Aug 2024, 14:14

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:57.807 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:39.204
Before features/support/hooks.rb:269 0.006
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 1:1.463
When I start Tails from USB drive "old" with network unplugged 1:32.352
Then the boot device has safe access rights 2.985
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 7.787
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.957
Before features/support/hooks.rb:269 0.006
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login 1:33.372
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 32.892
And I take note of which tps features are available 1.555
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.590
After features/support/hooks.rb:326 0.235
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.124
Before features/support/hooks.rb:269 0.006
Given a computer 0.418
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.716
Then Tails is running from USB drive "old" 0.423
And all tps features are active 2.613
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.884
And all persistent directories from the old Tails version have safe access rights 2.615
And I take note of which tps features are available 0.585
And I shutdown Tails and wait for the computer to power off 4.089
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.743
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.013
Tags: @product
3:2.903
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 28.427
And I log in to a new session 24.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.493
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.414
Then the running Tails is installed on USB drive "to_upgrade" 23.381
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.302
After features/support/hooks.rb:326 2.356
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.334
Before features/support/hooks.rb:269 0.007
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.888
Then all tps features from the old Tails version are active 1.781
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.527
And the expected persistent files created with the old Tails version are present in the filesystem 1.817
And all persistent directories from the old Tails version have safe access rights 2.704
After features/support/hooks.rb:326 1.093
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.260
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 14.566
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.078
And Tor is ready 20.919
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.335
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.591
Given I shutdown Tails and wait for the computer to power off 11.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.471
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.428
# 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.376
When the network is plugged 0.097
And Tor is ready 19.095
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.341
Given I shutdown Tails and wait for the computer to power off 6.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.943
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
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.403
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.082
And Tor is ready 20.410
Then the Upgrader considers the system as up-to-date 0.337
# 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.270
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.267
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
46.022
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 13.939
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.048
But a current signing key is available on our website 0.000
When the network is plugged 0.175
And Tor is ready 22.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.594
After features/support/hooks.rb:326 0.945
After features/support/hooks.rb:100 0.000