Project Number Date
test_Tails_ISO_devel 3537 08 Oct 2024, 19:31

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:29.552 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:19.137
Before features/support/hooks.rb:269 0.008
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 38.836
When I start Tails from USB drive "old" with network unplugged 1:34.490
Then the boot device has safe access rights 3.422
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.475
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.103
Before features/support/hooks.rb:269 0.009
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:28.698
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 37.194
And I take note of which tps features are available 2.131
Then a Tails persistence partition exists on USB drive "old" 0.983
And I shutdown Tails and wait for the computer to power off 9.494
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.493
Before features/support/hooks.rb:269 0.005
Given a computer 1.454
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.231
Then Tails is running from USB drive "old" 1.115
And all tps features are active 3.817
When I write some files expected to persist 1.819
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.738
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.590
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.554
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.015
Tags: @product
2:37.675
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.386
And I log in to a new session 22.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.991
And I plug USB drive "to_upgrade" 2.598
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.138
Then the running Tails is installed on USB drive "to_upgrade" 22.891
And I unplug USB drive "to_upgrade" 0.289
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:326 2.811
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.596
Before features/support/hooks.rb:269 0.009
Given a computer 0.915
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.754
Then all tps features from the old Tails version are active 1.709
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.509
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
7:57.743
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 15.573
And no SquashFS delta is installed 0.392
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.528
When the network is plugged 0.072
And Tor is ready 22.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.362
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.906
Given I shutdown Tails and wait for the computer to power off 11.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.169
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 4.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.129
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.436
When the network is plugged 0.534
And Tor is ready 21.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.123
Given I shutdown Tails and wait for the computer to power off 1:0.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.164
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 3.906
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.224
And Tor is ready 19.467
Then the Upgrader considers the system as up-to-date 0.321
# 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.854
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.015
After features/support/hooks.rb:326 0.867
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
38.802
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 10.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 1.566
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 19.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.853
After features/support/hooks.rb:326 0.915
After features/support/hooks.rb:100 0.000