Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 16 03 Aug 2024, 16:22

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 19:49.820 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:50.567
Before features/support/hooks.rb:269 0.005
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 57.381
When I start Tails from USB drive "old" with network unplugged 1:47.515
Then the boot device has safe access rights 3.291
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:326 7.352
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.073
Before features/support/hooks.rb:269 0.005
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:24.841
Then Tails is running from USB drive "old" 0.422
And I create a persistent partition 32.536
And I take note of which tps features are available 1.733
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.012
Tags: @product
2:50.387
Before features/support/hooks.rb:269 0.009
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.418
Then Tails is running from USB drive "old" 0.415
And all tps features are active 2.207
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.191
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.429
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.769
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 12.967
And I log in to a new session 20.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.644
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.828
Then the running Tails is installed on USB drive "to_upgrade" 21.976
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 2.410
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.303
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.893
Then all tps features from the old Tails version are active 1.836
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.692
And all persistent directories from the old Tails version have safe access rights 2.636
After features/support/hooks.rb:326 0.629
After features/support/hooks.rb:100 0.010
6:27.674
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 10.942
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.794
When the network is plugged 0.034
And Tor is ready 22.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.625
Given I shutdown Tails and wait for the computer to power off 8.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.733
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.876
And the file system changes introduced in version 6.2~testoverlayfs are present 0.488
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.279
When the network is plugged 0.041
And Tor is ready 18.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.406
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.523
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.067
And Tor is ready 19.866
Then the Upgrader considers the system as up-to-date 0.330
# 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.785
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.019
39.045
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 10.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.911
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 20.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.493
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.000