Project Number Date
test_Tails_ISO_devel 3451 08 Jul 2024, 16:08

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:8.592 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:15.826
Before features/support/hooks.rb:269 0.006
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 29.716
When I start Tails from USB drive "old" with network unplugged 1:40.627
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.792
After features/support/hooks.rb:100 0.013
Tags: @product
2:4.206
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:20.779
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.299
And I take note of which tps features are available 1.318
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.824
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.016
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.063
When I write some files expected to persist 1.671
# 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.521
And all persistent directories from the old Tails version have safe access rights 2.580
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.329
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.327
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.013
Tags: @product
2:32.299
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 11.321
And I log in to a new session 18.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.430
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.329
Then the running Tails is installed on USB drive "to_upgrade" 22.134
And I unplug USB drive "to_upgrade" 0.338
And I unplug USB drive "__internal" 0.422
After features/support/hooks.rb:326 6.989
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.097
Before features/support/hooks.rb:269 0.008
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.347
Then all tps features from the old Tails version are active 1.703
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.591
After features/support/hooks.rb:326 1.141
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:54.899
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.796
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.036
And Tor is ready 20.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.829
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.535
Given I shutdown Tails and wait for the computer to power off 8.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.663
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.242
When the network is plugged 0.078
And Tor is ready 47.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.622
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.668
Given I shutdown Tails and wait for the computer to power off 6.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.778
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.050
And Tor is ready 20.660
Then the Upgrader considers the system as up-to-date 0.369
# 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.397
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:326 0.902
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
59.439
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.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.656
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 0.891
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 46.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.605
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.000