Project Number Date
test_Tails_ISO_devel 3524 29 Sep 2024, 12:23

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:20.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:0.294
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.224
When I start Tails from USB drive "old" with network unplugged 1:27.027
Then the boot device has safe access rights 2.847
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 8.225
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.752
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:19.590
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 30.618
And I take note of which tps features are available 1.942
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.279
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
2:43.185
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.903
Then Tails is running from USB drive "old" 0.338
And all tps features are active 1.989
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.374
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.206
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.536
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.842
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 12.652
And I log in to a new session 20.018
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.440
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.088
Then the running Tails is installed on USB drive "to_upgrade" 17.844
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 1.351
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.905
Before features/support/hooks.rb:269 0.006
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.729
Then all tps features from the old Tails version are active 1.585
And Tails is running from USB drive "to_upgrade" 0.471
And the boot device has safe access rights 3.144
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.348
After features/support/hooks.rb:326 0.964
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:16.158
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.680
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
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.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.074
And Tor is ready 22.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.227
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.007
Given I shutdown Tails and wait for the computer to power off 10.868
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.938
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.286
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.269
When the network is plugged 0.073
And Tor is ready 18.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.977
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.966
Given I shutdown Tails and wait for the computer to power off 4.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.007
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.067
And Tor is ready 17.477
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 13.564
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.817
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 9.932
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.692
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 16.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.473
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.000