Project Number Date
test_Tails_ISO_stable 5039 21 Aug 2024, 08:37

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:39.956 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:56.500
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 1:15.667
When I start Tails from USB drive "old" with network unplugged 1:35.382
Then the boot device has safe access rights 3.123
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.277
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.673
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:28.656
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.744
And I take note of which tps features are available 1.709
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 6.151
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.982
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.394
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.167
When I write some files expected to persist 2.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.524
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.341
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.374
And I log in to a new session 17.992
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.541
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.276
Then the running Tails is installed on USB drive "to_upgrade" 24.334
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 1.931
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.934
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.207
Then all tps features from the old Tails version are active 3.425
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 4.204
And the expected persistent files created with the old Tails version are present in the filesystem 1.301
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:1.969
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.798
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.621
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.601
When the network is plugged 0.149
And Tor is ready 27.249
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.278
Given I shutdown Tails and wait for the computer to power off 27.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.311
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.277
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.428
# 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.298
When the network is plugged 0.110
And Tor is ready 19.071
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.277
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.657
Given I shutdown Tails and wait for the computer to power off 4.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.458
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.411
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.072
And Tor is ready 19.920
Then the Upgrader considers the system as up-to-date 0.329
# 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.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.060
After features/support/hooks.rb:326 0.873
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.553
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 14.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 1.858
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 19.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.420
After features/support/hooks.rb:326 1.772
After features/support/hooks.rb:100 0.000