Project Number Date
test_Tails_ISO_stable 4871 04 Jun 2024, 16:42

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:19.543 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:4.156
Before features/support/hooks.rb:265 0.008
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.557
When I start Tails from USB drive "old" with network unplugged 1:28.435
Then the boot device has safe access rights 2.825
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:311 7.188
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.731
Before features/support/hooks.rb:265 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:29.992
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 37.562
And I take note of which tps features are available 1.356
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:311 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.343
Before features/support/hooks.rb:265 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.826
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.369
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.538
And all persistent directories from the old Tails version have safe access rights 2.819
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.319
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.496
After features/support/hooks.rb:311 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.238
Before features/support/hooks.rb:265 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 10.436
And I log in to a new session 20.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.603
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.008
Then the running Tails is installed on USB drive "to_upgrade" 17.628
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:311 6.633
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.748
Before features/support/hooks.rb:265 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.282
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.961
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.876
After features/support/hooks.rb:311 0.598
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:21.508
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.845
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
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.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.036
And Tor is ready 18.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.298
Given I shutdown Tails and wait for the computer to power off 8.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.146
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# 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.280
When the network is plugged 0.035
And Tor is ready 17.025
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.695
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.752
Given I shutdown Tails and wait for the computer to power off 4.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.022
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.903
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.080
# 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.407
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.035
And Tor is ready 20.035
Then the Upgrader considers the system as up-to-date 0.329
# 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.633
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.042
After features/support/hooks.rb:311 0.779
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
57.817
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.044
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 46.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.598
After features/support/hooks.rb:311 0.655
After features/support/hooks.rb:100 0.000