Project Number Date
test_Tails_ISO_stable 4887 12 Jun 2024, 18: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 18:58.420 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:7.417
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.734
When I start Tails from USB drive "old" with network unplugged 1:30.425
Then the boot device has safe access rights 2.933
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:320 3.561
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.837
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:33.688
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 36.644
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 12.567
After features/support/hooks.rb:320 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.081
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.463
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.880
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.330
And all persistence configuration files have safe access rights 0.569
And all persistent directories from the old Tails version have safe access rights 2.544
And I take note of which tps features are available 0.396
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.285
After features/support/hooks.rb:320 0.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.660
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.009
And I log in to a new session 17.662
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.631
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.266
Then the running Tails is installed on USB drive "to_upgrade" 15.215
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:320 3.012
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.516
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.395
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.007
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 2.442
After features/support/hooks.rb:320 0.639
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:30.754
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 10.695
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.621
And Tor is ready 18.761
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.823
Given I shutdown Tails and wait for the computer to power off 9.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.631
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.271
When the network is plugged 0.036
And Tor is ready 15.155
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.591
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.758
Given I shutdown Tails and wait for the computer to power off 6.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.162
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.046
And Tor is ready 19.706
Then the Upgrader considers the system as up-to-date 0.320
# 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.296
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:320 0.807
After features/support/hooks.rb:100 0.065
Tags: @product @automatic_upgrade
34.151
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 10.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.080
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 15.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.260
After features/support/hooks.rb:320 1.382
After features/support/hooks.rb:100 0.000