Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 28 19 Aug 2024, 17:11

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 22:14.574 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
3:3.919
Before features/support/hooks.rb:269 0.007
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 1:0.124
When I start Tails from USB drive "old" with network unplugged 1:58.273
Then the boot device has safe access rights 3.163
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.593
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.883
Before features/support/hooks.rb:269 0.006
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login 1:25.200
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 42.038
And I take note of which tps features are available 1.682
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.446
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.522
Before features/support/hooks.rb:269 0.006
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.706
Then Tails is running from USB drive "old" 1.514
And all tps features are active 3.194
When I write some files expected to persist 3.842
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 2.944
And I take note of which tps features are available 0.612
And I shutdown Tails and wait for the computer to power off 4.687
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.003
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.078
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 19.100
And I log in to a new session 21.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.892
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.799
Then the running Tails is installed on USB drive "to_upgrade" 22.193
And I unplug USB drive "to_upgrade" 0.293
And I unplug USB drive "__internal" 0.297
After features/support/hooks.rb:326 7.985
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.753
Before features/support/hooks.rb:269 0.006
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.176
Then all tps features from the old Tails version are active 4.149
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.606
And the expected persistent files created with the old Tails version are present in the filesystem 1.634
And all persistent directories from the old Tails version have safe access rights 2.547
After features/support/hooks.rb:326 0.894
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:58.967
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 32.848
And no SquashFS delta is installed 0.516
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.175
And Tor is ready 50.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.675
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.193
Given I shutdown Tails and wait for the computer to power off 16.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.355
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.722
And the file system changes introduced in version 6.2~testoverlayfs are present 0.387
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.310
When the network is plugged 0.070
And Tor is ready 22.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.639
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.134
Given I shutdown Tails and wait for the computer to power off 6.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.424
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.578
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.133
And Tor is ready 17.604
Then the Upgrader considers the system as up-to-date 11.045
# 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.570
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.053
After features/support/hooks.rb:326 0.887
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.450
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.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.695
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.917
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.985
After features/support/hooks.rb:326 0.923
After features/support/hooks.rb:100 0.000