Project Number Date
test_Tails_ISO_devel 3446 04 Jul 2024, 12:14

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:30.621 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:14.657
Before features/support/hooks.rb:269 0.008
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 27.189
When I start Tails from USB drive "old" with network unplugged 1:42.417
Then the boot device has safe access rights 2.822
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.544
After features/support/hooks.rb:100 0.011
Tags: @product
1:59.681
Before features/support/hooks.rb:269 0.008
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:18.185
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 30.534
And I take note of which tps features are available 1.497
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 8.171
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.929
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.089
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.984
When I write some files expected to persist 1.600
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.378
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.145
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.616
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.754
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.125
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.497
And I log in to a new session 16.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.447
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.311
Then the running Tails is installed on USB drive "to_upgrade" 15.435
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.174
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.218
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.355
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.032
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 2.397
After features/support/hooks.rb:326 0.639
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:20.138
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 16.057
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.041
And Tor is ready 21.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.234
Given I shutdown Tails and wait for the computer to power off 1:12.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.688
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.083
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.311
When the network is plugged 0.039
And Tor is ready 18.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.010
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.697
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.208
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.049
And Tor is ready 18.338
Then the Upgrader considers the system as up-to-date 0.317
# 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 13.395
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.922
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.869
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 9.858
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 18.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.059
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.000