Project Number Date
test_Tails_ISO_stable 4907 20 Jun 2024, 19:49

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:38.718 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:21.395
Before features/support/hooks.rb:269 0.007
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.247
When I start Tails from USB drive "old" with network unplugged 1:47.059
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.238
After features/support/hooks.rb:326 7.228
After features/support/hooks.rb:100 0.010
Tags: @product
2:1.272
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:19.136
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.106
And I take note of which tps features are available 1.495
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.205
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.201
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.625
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.136
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.384
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.053
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.788
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 10.061
And I log in to a new session 16.862
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.338
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.647
Then the running Tails is installed on USB drive "to_upgrade" 15.093
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 3.420
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.419
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.300
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.211
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:326 0.933
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.078
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 14.262
And no SquashFS delta is installed 0.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.046
And Tor is ready 22.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.859
Given I shutdown Tails and wait for the computer to power off 8.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.555
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.271
When the network is plugged 0.055
And Tor is ready 18.063
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.735
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.269
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.924
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.421
When the network is plugged 0.047
And Tor is ready 18.855
Then the Upgrader considers the system as up-to-date 0.312
# 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 14.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.929
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.561
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.625
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.990
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 20.169
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.384
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.000