Project Number Date
test_Tails_ISO_stable 5137 03 Oct 2024, 13:57

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:54.400 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:53.214
Before features/support/hooks.rb:269 0.007
Given a computer 0.302
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 1:3.697
When I start Tails from USB drive "old" with network unplugged 1:43.724
Then the boot device has safe access rights 3.246
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 3.607
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.255
Before features/support/hooks.rb:269 0.005
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:26.929
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 35.418
And I take note of which tps features are available 1.864
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 8.555
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.007
Tags: @product
3:1.495
Before features/support/hooks.rb:269 0.004
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.273
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.153
When I write some files expected to persist 2.087
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.854
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.177
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.120
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.481
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.094
And I log in to a new session 22.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.864
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.289
Then the running Tails is installed on USB drive "to_upgrade" 24.622
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.968
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.048
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.296
Then all tps features from the old Tails version are active 1.775
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 3.429
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:326 0.641
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:58.396
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 13.306
And no SquashFS delta is installed 0.315
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.590
When the network is plugged 0.079
And Tor is ready 22.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.462
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.304
Given I shutdown Tails and wait for the computer to power off 11.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.434
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.274
When the network is plugged 0.089
And Tor is ready 20.984
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.293
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.684
Given I shutdown Tails and wait for the computer to power off 4.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.276
Then Tails is running version 6.3~testoverlayfs 0.043
And all tps features are active 2.549
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.107
And Tor is ready 18.060
Then the Upgrader considers the system as up-to-date 0.326
# 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.387
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.204
After features/support/hooks.rb:326 0.881
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.510
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.940
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.707
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 2.065
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 20.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.977
After features/support/hooks.rb:326 1.418
After features/support/hooks.rb:100 0.000