Project Number Date
test_Tails_ISO_devel 3505 06 Sep 2024, 13:05

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:14.572 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:11.997
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.869
When I start Tails from USB drive "old" with network unplugged 1:35.708
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.198
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:23.339
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.429
And I take note of which tps features are available 1.554
Then a Tails persistence partition exists on USB drive "old" 0.936
And I shutdown Tails and wait for the computer to power off 8.364
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.921
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.325
Then Tails is running from USB drive "old" 0.422
And all tps features are active 2.166
When I write some files expected to persist 1.778
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.855
And I take note of which tps features are available 0.524
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.637
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.007
Tags: @product
2:27.797
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.586
And I log in to a new session 18.831
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.463
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.363
Then the running Tails is installed on USB drive "to_upgrade" 20.769
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 6.858
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.839
Before features/support/hooks.rb:269 0.033
Given a computer 0.277
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.423
Then all tps features from the old Tails version are active 1.673
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.385
And the expected persistent files created with the old Tails version are present in the filesystem 1.450
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:326 0.958
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:44.985
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 12.790
And no SquashFS delta is installed 0.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
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.452
When the network is plugged 0.077
And Tor is ready 47.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.466
Given I shutdown Tails and wait for the computer to power off 8.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.175
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.171
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.394
# 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.270
When the network is plugged 0.075
And Tor is ready 18.818
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.076
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.686
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.075
And Tor is ready 19.330
Then the Upgrader considers the system as up-to-date 0.318
# 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.177
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.853
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.832
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 11.016
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.898
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 15.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.556
After features/support/hooks.rb:326 0.666
After features/support/hooks.rb:100 0.000