Project Number Date
test_Tails_ISO_stable 4899 18 Jun 2024, 16:30

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:13.541 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:15.271
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 29.896
When I start Tails from USB drive "old" with network unplugged 1:39.634
Then the boot device has safe access rights 3.360
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:320 3.666
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.438
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login 1:23.785
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 32.730
And I take note of which tps features are available 1.628
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.773
After features/support/hooks.rb:320 0.177
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.507
Before features/support/hooks.rb:269 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.062
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.215
When I write some files expected to persist 1.609
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 4.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.668
After features/support/hooks.rb:320 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.735
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.782
And I log in to a new session 18.655
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.586
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.061
Then the running Tails is installed on USB drive "to_upgrade" 20.781
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:320 4.720
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.751
Before features/support/hooks.rb:269 0.005
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.590
Then all tps features from the old Tails version are active 2.209
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.480
And all persistent directories from the old Tails version have safe access rights 2.456
After features/support/hooks.rb:320 1.109
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:37.701
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.636
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
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.414
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.053
And Tor is ready 20.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.266
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.059
Given I shutdown Tails and wait for the computer to power off 11.057
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.526
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.202
When the network is plugged 0.040
And Tor is ready 18.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.263
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.010
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.610
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.027
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.033
And Tor is ready 19.185
Then the Upgrader considers the system as up-to-date 0.338
# 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.380
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:320 0.741
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.134
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 9.909
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.989
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 20.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.735
After features/support/hooks.rb:320 0.667
After features/support/hooks.rb:100 0.000