Project Number Date
test_Tails_ISO_stable 5209 21 Oct 2024, 19:32

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 20:8.765 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:9.793
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.736
When I start Tails from USB drive "old" with network unplugged 1:32.303
Then the boot device has safe access rights 3.380
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.544
After features/support/hooks.rb:100 0.076
Tags: @product
2:9.010
Before features/support/hooks.rb:269 0.005
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:26.806
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 32.234
And I take note of which tps features are available 1.901
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 6.532
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.837
Before features/support/hooks.rb:269 0.004
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.174
Then Tails is running from USB drive "old" 0.876
And all tps features are active 2.914
When I write some files expected to persist 2.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.611
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.340
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.732
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.901
And I log in to a new session 19.873
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.870
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.780
Then the running Tails is installed on USB drive "to_upgrade" 22.391
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 7.227
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.509
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.408
Then all tps features from the old Tails version are active 1.969
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.527
And the expected persistent files created with the old Tails version are present in the filesystem 1.475
And all persistent directories from the old Tails version have safe access rights 2.525
After features/support/hooks.rb:326 0.950
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:46.701
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 20.116
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.640
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.068
And Tor is ready 25.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.276
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.655
Given I shutdown Tails and wait for the computer to power off 11.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.760
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.397
# 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.293
When the network is plugged 0.071
And Tor is ready 18.729
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.480
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.874
Given I shutdown Tails and wait for the computer to power off 4.383
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.254
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.429
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.074
And Tor is ready 17.318
Then the Upgrader considers the system as up-to-date 0.339
# 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.958
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.970
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:4.180
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.446
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.103
And Tor is ready 50.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:326 0.626
After features/support/hooks.rb:100 0.000