Project Number Date
test_Tails_ISO_stable 4869 03 Jun 2024, 22:22

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 18:22.531 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
1:56.780
Before features/support/hooks.rb:265 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.121
When I start Tails from USB drive "old" with network unplugged 1:22.591
Then the boot device has safe access rights 2.843
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:311 3.587
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.081
Before features/support/hooks.rb:265 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:20.360
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 33.520
And I take note of which tps features are available 1.475
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.398
After features/support/hooks.rb:311 0.175
After features/support/hooks.rb:100 0.021
Tags: @product
2:47.466
Before features/support/hooks.rb:265 0.007
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.053
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.969
When I write some files expected to persist 1.607
# 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.438
And all persistent directories from the old Tails version have safe access rights 2.337
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.466
After features/support/hooks.rb:311 0.134
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.200
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.115
And I log in to a new session 17.548
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.438
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.962
Then the running Tails is installed on USB drive "to_upgrade" 19.270
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:311 1.913
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.735
Before features/support/hooks.rb:265 0.007
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.760
Then all tps features from the old Tails version are active 1.514
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 2.840
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.532
After features/support/hooks.rb:311 0.766
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:18.788
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.659
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.035
And Tor is ready 18.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.159
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.710
Given I shutdown Tails and wait for the computer to power off 8.586
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.661
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.257
When the network is plugged 0.036
And Tor is ready 19.260
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.966
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.049
Given I shutdown Tails and wait for the computer to power off 4.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.716
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.577
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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.033
And Tor is ready 18.028
Then the Upgrader considers the system as up-to-date 0.303
# 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.078
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.892
After features/support/hooks.rb:311 0.712
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.478
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.820
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.043
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 19.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.462
After features/support/hooks.rb:311 0.699
After features/support/hooks.rb:100 0.000