Project Number Date
test_Tails_ISO_devel 3466 07 Aug 2024, 12:43

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 19:38.008 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:13.522
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 36.276
When I start Tails from USB drive "old" with network unplugged 1:32.081
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.555
After features/support/hooks.rb:100 0.037
Tags: @product
2:6.245
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:23.088
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 31.938
And I take note of which tps features are available 1.538
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 8.243
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.937
Before features/support/hooks.rb:269 0.005
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.785
Then Tails is running from USB drive "old" 0.369
And all tps features are active 3.261
When I write some files expected to persist 1.900
# 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.448
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.821
And I shutdown Tails and wait for the computer to power off 4.153
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.023
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.529
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.774
And I log in to a new session 18.620
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.317
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.115
Then the running Tails is installed on USB drive "to_upgrade" 23.885
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 1.886
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.576
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.226
Then all tps features from the old Tails version are active 1.794
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.673
And the expected persistent files created with the old Tails version are present in the filesystem 1.593
And all persistent directories from the old Tails version have safe access rights 2.690
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.822
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.748
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.053
And Tor is ready 19.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.857
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.061
Given I shutdown Tails and wait for the computer to power off 10.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.507
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.275
When the network is plugged 0.044
And Tor is ready 15.151
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.022
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.286
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.548
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.178
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.047
And Tor is ready 17.973
Then the Upgrader considers the system as up-to-date 0.359
# 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 17.323
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.088
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.375
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 9.333
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.709
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 17.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.361
After features/support/hooks.rb:326 1.355
After features/support/hooks.rb:100 0.000