Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 69 18 Sep 2024, 23:59

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:1.836 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:11.663
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.089
And I write an old version of the Tails USB image to disk "old" 32.461
When I start Tails from USB drive "old" with network unplugged 1:33.509
Then the boot device has safe access rights 3.261
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.260
After features/support/hooks.rb:326 8.086
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.710
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:24.095
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 30.059
And I take note of which tps features are available 1.702
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 8.435
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.725
Before features/support/hooks.rb:269 0.003
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.996
Then Tails is running from USB drive "old" 0.353
And all tps features are active 2.106
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.350
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 4.380
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.308
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.335
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 12.147
And I log in to a new session 21.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.500
And I plug USB drive "to_upgrade" 2.447
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.934
Then the running Tails is installed on USB drive "to_upgrade" 24.595
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.309
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.661
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.938
Then all tps features from the old Tails version are active 1.668
And Tails is running from USB drive "to_upgrade" 0.531
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.439
And all persistent directories from the old Tails version have safe access rights 2.349
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:27.337
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 12.197
And no SquashFS delta is installed 0.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.543
When the network is plugged 0.068
And Tor is ready 22.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.575
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.554
Given I shutdown Tails and wait for the computer to power off 10.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.481
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.364
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.362
# 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.270
When the network is plugged 0.092
And Tor is ready 18.101
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.943
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.588
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.581
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.406
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.503
When the network is plugged 0.066
And Tor is ready 19.490
Then the Upgrader considers the system as up-to-date 0.323
# 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.248
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.172
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.402
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 11.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.151
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.233
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.000