Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 2 24 Jul 2024, 16:43

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:19.822 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:51.760
Before features/support/hooks.rb:269 0.006
Given a computer 0.468
And I create a 7200 MiB disk named "old" 0.648
And I plug USB drive "old" 1.146
And I write an old version of the Tails USB image to disk "old" 50.458
When I start Tails from USB drive "old" with network unplugged 1:54.190
Then the boot device has safe access rights 3.694
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.676
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.146
Before features/support/hooks.rb:269 0.012
Given a computer 0.820
And I start Tails from USB drive "old" with network unplugged and I login 1:26.705
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 33.535
And I take note of which tps features are available 2.239
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 6.546
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.064
Before features/support/hooks.rb:269 0.005
Given a computer 0.373
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.513
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.765
When I write some files expected to persist 2.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.616
And I shutdown Tails and wait for the computer to power off 4.426
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.379
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.922
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 24.993
And I log in to a new session 22.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.648
And I plug USB drive "to_upgrade" 2.614
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.935
Then the running Tails is installed on USB drive "to_upgrade" 22.773
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.303
After features/support/hooks.rb:326 3.527
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.871
Before features/support/hooks.rb:269 0.007
Given a computer 0.285
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.966
Then all tps features from the old Tails version are active 4.194
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.422
And the expected persistent files created with the old Tails version are present in the filesystem 1.711
And all persistent directories from the old Tails version have safe access rights 2.942
After features/support/hooks.rb:326 1.042
After features/support/hooks.rb:100 0.015
7:8.787
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.056
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.456
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.266
And Tor is ready 21.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.724
Given I shutdown Tails and wait for the computer to power off 9.014
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.659
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
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.340
# 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.390
When the network is plugged 0.210
And Tor is ready 46.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.803
Given I shutdown Tails and wait for the computer to power off 4.670
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.905
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.775
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.524
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.424
When the network is plugged 0.053
And Tor is ready 18.978
Then the Upgrader considers the system as up-to-date 0.357
# 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.728
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.996
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.023
39.270
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 11.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the signing key used by the Upgrader is outdated 0.878
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 20.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.729
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.000