Project Number Date
test_Tails_ISO_devel 3288 19 Feb 2024, 15:17

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 21:10.215 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
1:38.989
Before features/support/hooks.rb:245 0.004
Given a computer 0.146
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 20.622
When I start Tails from USB drive "old" with network unplugged 1:13.155
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 6.627
After features/support/hooks.rb:75 0.009
Tags: @product
2:14.921
Before features/support/hooks.rb:245 0.005
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login 1:21.215
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 42.855
And I take note of which tps features are available 1.575
Then a Tails persistence partition exists on USB drive "old" 0.740
And I shutdown Tails and wait for the computer to power off 8.067
After features/support/hooks.rb:291 0.263
After features/support/hooks.rb:75 0.009
Tags: @product
3:13.567
Before features/support/hooks.rb:245 0.004
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:47.223
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.832
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.369
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 2.332
And I take note of which tps features are available 0.264
And I shutdown Tails and wait for the computer to power off 4.062
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.754
After features/support/hooks.rb:291 0.125
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.615
Before features/support/hooks.rb:245 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 9.146
And I log in to a new session 18.447
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.785
Then the running Tails is installed on USB drive "to_upgrade" 15.772
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:291 3.598
After features/support/hooks.rb:75 0.000
Tags: @product
2:53.744
Before features/support/hooks.rb:245 0.007
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:43.991
Then all tps features from the old Tails version are active 1.422
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.930
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.387
After features/support/hooks.rb:291 0.660
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
8:1.319
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.573
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.033
And Tor is ready 17.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.973
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.693
Given I shutdown Tails and wait for the computer to power off 8.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.001
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.846
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.292
When the network is plugged 0.024
And Tor is ready 21.198
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.265
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.934
Given I shutdown Tails and wait for the computer to power off 5.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.428
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.772
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.021
And Tor is ready 18.624
Then the Upgrader considers the system as up-to-date 0.265
# 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.701
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.900
After features/support/hooks.rb:291 0.677
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
35.056
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.360
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.429
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 17.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.265
After features/support/hooks.rb:291 0.730
After features/support/hooks.rb:75 0.000