Project Number Date
test_Tails_ISO_stable 5153 07 Oct 2024, 18:20

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:32.414 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:6.091
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.518
When I start Tails from USB drive "old" with network unplugged 1:31.116
Then the boot device has safe access rights 3.101
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 7.207
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.030
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:29.393
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 30.755
And I take note of which tps features are available 2.808
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.593
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.615
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.048
Then Tails is running from USB drive "old" 0.924
And all tps features are active 2.028
When I write some files expected to persist 1.681
# 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.401
And all persistent directories from the old Tails version have safe access rights 2.884
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.442
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.326
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.665
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.151
And I log in to a new session 19.673
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.694
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.447
Then the running Tails is installed on USB drive "to_upgrade" 23.765
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:326 3.885
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.270
Before features/support/hooks.rb:269 0.008
Given a computer 0.294
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.779
Then all tps features from the old Tails version are active 2.056
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.621
And the expected persistent files created with the old Tails version are present in the filesystem 1.603
And all persistent directories from the old Tails version have safe access rights 3.522
After features/support/hooks.rb:326 1.305
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
7:25.540
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.414
And no SquashFS delta is installed 0.220
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.618
When the network is plugged 0.106
And Tor is ready 22.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.682
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.243
Given I shutdown Tails and wait for the computer to power off 8.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.512
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.336
When the network is plugged 0.316
And Tor is ready 18.553
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.672
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.456
Given I shutdown Tails and wait for the computer to power off 6.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.268
Then Tails is running version 6.3~testoverlayfs 0.089
And all tps features are active 6.402
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.334
When the network is plugged 0.613
And Tor is ready 19.249
Then the Upgrader considers the system as up-to-date 10.915
# 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.763
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.153
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.201
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.778
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.951
But a current signing key is available on our website 0.000
When the network is plugged 0.610
And Tor is ready 16.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.525
After features/support/hooks.rb:326 1.131
After features/support/hooks.rb:100 0.000