Project Number Date
test_Tails_ISO_stable 5099 13 Sep 2024, 13:40

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:31.473 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:20.267
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.946
When I start Tails from USB drive "old" with network unplugged 1:45.634
Then the boot device has safe access rights 3.271
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.400
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.765
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.975
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:28.358
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 35.238
And I take note of which tps features are available 2.028
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.842
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.743
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.853
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.023
When I write some files expected to persist 2.095
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.590
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.687
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.865
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.586
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.145
And I log in to a new session 20.287
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.545
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.529
Then the running Tails is installed on USB drive "to_upgrade" 25.042
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 2.945
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.143
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.206
Then all tps features from the old Tails version are active 1.694
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.437
And the expected persistent files created with the old Tails version are present in the filesystem 2.665
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:19.158
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 26.115
And no SquashFS delta is installed 0.316
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.752
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.071
And Tor is ready 21.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.928
Given I shutdown Tails and wait for the computer to power off 1:35.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.921
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.313
When the network is plugged 0.085
And Tor is ready 19.362
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.709
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.357
Given I shutdown Tails and wait for the computer to power off 4.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.223
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.954
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.426
And Tor is ready 19.366
Then the Upgrader considers the system as up-to-date 0.335
# 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.938
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.142
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.597
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.707
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.783
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.993
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.450
After features/support/hooks.rb:326 1.182
After features/support/hooks.rb:100 0.000