Project Number Date
test_Tails_ISO_stable 4845 16 May 2024, 17:35

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:52.474 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:6.197
Before features/support/hooks.rb:259 0.005
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 29.694
When I start Tails from USB drive "old" with network unplugged 1:31.296
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:305 6.911
After features/support/hooks.rb:89 0.017
Tags: @product
2:8.463
Before features/support/hooks.rb:259 0.005
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:21.209
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 35.927
And I take note of which tps features are available 1.459
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 8.459
After features/support/hooks.rb:305 0.176
After features/support/hooks.rb:89 0.009
Tags: @product
2:53.837
Before features/support/hooks.rb:259 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.795
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.094
When I write some files expected to persist 1.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.325
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.308
After features/support/hooks.rb:305 0.097
After features/support/hooks.rb:89 0.007
Tags: @product
2:34.175
Before features/support/hooks.rb:259 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 12.297
And I log in to a new session 21.903
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.710
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.093
Then the running Tails is installed on USB drive "to_upgrade" 22.324
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:305 1.963
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.518
Before features/support/hooks.rb:259 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.540
Then all tps features from the old Tails version are active 4.417
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.849
And the expected persistent files created with the old Tails version are present in the filesystem 1.611
And all persistent directories from the old Tails version have safe access rights 2.565
After features/support/hooks.rb:305 0.780
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:22.212
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.713
And no SquashFS delta is installed 0.467
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.072
And Tor is ready 17.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.110
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.403
Given I shutdown Tails and wait for the computer to power off 8.998
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.438
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
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.363
# 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.195
And Tor is ready 16.598
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.747
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.102
Given I shutdown Tails and wait for the computer to power off 6.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.755
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.944
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.044
And Tor is ready 17.296
Then the Upgrader considers the system as up-to-date 0.344
# 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.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.202
After features/support/hooks.rb:305 1.026
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
32.068
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.715
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.764
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 16.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.196
After features/support/hooks.rb:305 1.210
After features/support/hooks.rb:89 0.000