Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 35 22 Aug 2024, 20:02

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:0.416 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:23.809
Before features/support/hooks.rb:269 0.010
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.912
When I start Tails from USB drive "old" with network unplugged 1:45.234
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 7.714
After features/support/hooks.rb:100 0.013
Tags: @product
2:9.257
Before features/support/hooks.rb:269 0.010
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:24.265
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.292
And I take note of which tps features are available 2.476
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.774
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.291
Before features/support/hooks.rb:269 0.009
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.729
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.166
When I write some files expected to persist 2.229
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.305
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.586
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.473
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.248
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.012
Tags: @product
2:37.663
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.348
And I log in to a new session 21.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.784
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.330
Then the running Tails is installed on USB drive "to_upgrade" 23.525
And I unplug USB drive "to_upgrade" 0.318
And I unplug USB drive "__internal" 0.327
After features/support/hooks.rb:326 3.692
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.713
Before features/support/hooks.rb:269 0.012
Given a computer 0.326
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.902
Then all tps features from the old Tails version are active 2.120
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.622
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:326 0.876
After features/support/hooks.rb:100 0.067
6:51.047
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 12.243
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.086
And Tor is ready 21.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.528
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.069
Given I shutdown Tails and wait for the computer to power off 11.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.529
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.348
When the network is plugged 0.091
And Tor is ready 19.544
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.583
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.487
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.681
And only the 6.3~testoverlayfs SquashFS delta is installed 0.125
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.081
And Tor is ready 17.364
Then the Upgrader considers the system as up-to-date 10.841
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.013
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.019
37.633
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.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.982
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 20.478
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.544
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.000