Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 13 31 Jul 2024, 17:38

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:22.941 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:49.212
Before features/support/hooks.rb:269 0.004
Given a computer 1.151
And I create a 7200 MiB disk named "old" 0.612
And I plug USB drive "old" 1.233
And I write an old version of the Tails USB image to disk "old" 1:2.004
When I start Tails from USB drive "old" with network unplugged 1:38.365
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 1.723
After features/support/hooks.rb:326 4.021
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.071
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:31.904
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 32.610
And I take note of which tps features are available 1.644
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 6.481
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.767
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.373
Then Tails is running from USB drive "old" 0.509
And all tps features are active 2.240
When I write some files expected to persist 1.832
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.785
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.581
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.021
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.517
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 11.868
And I log in to a new session 18.951
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.562
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.167
Then the running Tails is installed on USB drive "to_upgrade" 24.038
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 3.630
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.011
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.373
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.775
And all persistent directories from the old Tails version have safe access rights 2.968
After features/support/hooks.rb:326 0.962
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.096
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 10.984
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.416
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.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.087
And Tor is ready 23.827
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.753
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.436
Given I shutdown Tails and wait for the computer to power off 8.860
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.050
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.469
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
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.375
# 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.267
When the network is plugged 0.040
And Tor is ready 19.417
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.275
Given I shutdown Tails and wait for the computer to power off 6.747
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.841
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.176
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.407
When the network is plugged 0.066
And Tor is ready 21.640
Then the Upgrader considers the system as up-to-date 0.371
# 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.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.068
After features/support/hooks.rb:326 0.950
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.264
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 9.796
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.822
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 46.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.638
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000