Project Number Date
test_Tails_ISO_devel 3428 16 Jun 2024, 13:07

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:47.496 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:10.180
Before features/support/hooks.rb:269 0.007
Given a computer 0.287
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.677
When I start Tails from USB drive "old" with network unplugged 1:35.121
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:315 0.971
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.270
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login 1:26.645
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 35.528
And I take note of which tps features are available 1.454
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.262
After features/support/hooks.rb:315 0.179
After features/support/hooks.rb:100 0.012
Tags: @product
2:52.982
Before features/support/hooks.rb:269 0.008
Given a computer 0.278
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.832
Then Tails is running from USB drive "old" 0.365
And all tps features are active 2.205
When I write some files expected to persist 1.883
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.368
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.463
After features/support/hooks.rb:315 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.397
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 12.310
And I log in to a new session 22.174
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.591
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.132
Then the running Tails is installed on USB drive "to_upgrade" 21.959
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:315 2.582
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.028
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.352
Then all tps features from the old Tails version are active 1.754
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:315 0.890
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:0.369
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 14.726
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.042
And Tor is ready 25.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.006
Given I shutdown Tails and wait for the computer to power off 8.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.740
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.811
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.260
When the network is plugged 0.035
And Tor is ready 17.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.801
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.194
Given I shutdown Tails and wait for the computer to power off 4.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.796
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.142
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.048
And Tor is ready 19.650
Then the Upgrader considers the system as up-to-date 0.316
# 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.678
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:315 1.278
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.267
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 12.675
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.091
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 17.081
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.036
After features/support/hooks.rb:315 0.712
After features/support/hooks.rb:100 0.000