Project Number Date
test_Tails_ISO_stable 5428 28 Jan 2025, 18:59

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 18:53.580 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:2.604
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.621
When I start Tails from USB drive "old" with network unplugged 1:26.060
Then the boot device has safe access rights 3.632
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 7.067
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.566
Before features/support/hooks.rb:269 0.008
Given a computer 0.308
And I start Tails from USB drive "old" with network unplugged and I login 1:29.198
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 32.040
And I take note of which tps features are available 1.436
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.469
After features/support/hooks.rb:326 0.237
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.314
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.431
Then Tails is running from USB drive "old" 1.066
And all tps features are active 2.231
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.726
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.382
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.682
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 12.802
And I log in to a new session 19.485
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.066
And I plug USB drive "to_upgrade" 2.515
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.679
Then the running Tails is installed on USB drive "to_upgrade" 21.705
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.307
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.428
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.455
Then all tps features from the old Tails version are active 1.723
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.620
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.656
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:13.523
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 11.405
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.076
And Tor is ready 19.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.410
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.608
Given I shutdown Tails and wait for the computer to power off 8.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.446
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.337
When the network is plugged 0.062
And Tor is ready 18.897
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.309
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.061
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.303
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.069
And Tor is ready 19.696
Then the Upgrader considers the system as up-to-date 0.286
# 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.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:326 0.809
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.461
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 9.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 20.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.092
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000