Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 64 04 Sep 2024, 19:05

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 21:9.273 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:25.423
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 38.883
When I start Tails from USB drive "old" with network unplugged 1:40.625
Then the boot device has safe access rights 3.380
And Tails is running from USB drive "old" 0.442
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 3.650
After features/support/hooks.rb:100 0.032
Tags: @product
2:20.770
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:35.902
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 32.926
And I take note of which tps features are available 1.934
Then a Tails persistence partition exists on USB drive "old" 0.896
And I shutdown Tails and wait for the computer to power off 8.489
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.158
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.531
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.099
When I write some files expected to persist 2.078
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 2.597
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.550
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.469
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.071
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 25.249
And I log in to a new session 21.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.069
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.496
Then the running Tails is installed on USB drive "to_upgrade" 23.845
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.404
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.345
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.670
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.188
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 1.259
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:17.459
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.426
And no SquashFS delta is installed 0.237
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.455
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.644
When the network is plugged 0.069
And Tor is ready 21.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.555
Given I shutdown Tails and wait for the computer to power off 11.093
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.914
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.459
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.341
When the network is plugged 0.073
And Tor is ready 21.906
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.621
Given I shutdown Tails and wait for the computer to power off 4.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.557
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 9.747
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.478
When the network is plugged 0.113
And Tor is ready 19.057
Then the Upgrader considers the system as up-to-date 0.336
# 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.422
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.465
After features/support/hooks.rb:326 0.881
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
37.044
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.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.627
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 1.064
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.605
After features/support/hooks.rb:326 1.249
After features/support/hooks.rb:100 0.000