Project Number Date
test_Tails_ISO_stable 5354 24 Dec 2024, 01:24

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:19.398 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:12.186
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.296
When I start Tails from USB drive "old" with network unplugged 1:34.427
Then the boot device has safe access rights 3.083
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 6.963
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.265
Before features/support/hooks.rb:269 0.006
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:31.143
Then Tails is running from USB drive "old" 0.435
And I create a persistent partition 35.350
And I take note of which tps features are available 1.753
Then a Tails persistence partition exists on USB drive "old" 0.991
And I shutdown Tails and wait for the computer to power off 9.353
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.007
Tags: @product
3:13.267
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.526
Then Tails is running from USB drive "old" 0.782
And all tps features are active 2.603
When I write some files expected to persist 2.158
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.833
And I take note of which tps features are available 0.656
And I shutdown Tails and wait for the computer to power off 4.840
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.909
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
3:11.767
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.587
And I log in to a new session 22.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.304
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.765
Then the running Tails is installed on USB drive "to_upgrade" 24.956
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 7.283
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.914
Before features/support/hooks.rb:269 0.007
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.634
Then all tps features from the old Tails version are active 1.771
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.305
And the expected persistent files created with the old Tails version are present in the filesystem 1.780
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:326 0.964
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:11.727
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 38.536
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.586
When the network is plugged 0.085
And Tor is ready 23.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.438
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 11.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.070
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.206
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# 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.519
When the network is plugged 0.080
And Tor is ready 19.400
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.201
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.094
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:7.734
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.241
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.395
When the network is plugged 0.091
And Tor is ready 21.301
Then the Upgrader considers the system as up-to-date 0.361
# 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 16.234
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.281
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
36.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.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.882
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.572
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.000