Project Number Date
test_Tails_ISO_stable 4891 15 Jun 2024, 13:16

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:48.731 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:19.569
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 32.186
When I start Tails from USB drive "old" with network unplugged 1:41.963
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:320 7.298
After features/support/hooks.rb:100 0.011
Tags: @product
2:21.121
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:34.145
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 34.991
And I take note of which tps features are available 1.853
Then a Tails persistence partition exists on USB drive "old" 0.933
And I shutdown Tails and wait for the computer to power off 8.624
After features/support/hooks.rb:320 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.564
Before features/support/hooks.rb:269 0.006
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.067
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.548
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
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.723
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 4.567
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.841
After features/support/hooks.rb:320 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.278
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 11.769
And I log in to a new session 20.936
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.561
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.002
Then the running Tails is installed on USB drive "to_upgrade" 20.028
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:320 1.974
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.850
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.534
Then all tps features from the old Tails version are active 1.678
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.266
And the expected persistent files created with the old Tails version are present in the filesystem 1.380
And all persistent directories from the old Tails version have safe access rights 2.422
After features/support/hooks.rb:320 0.839
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
7:42.338
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 12.356
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.152
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.030
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.047
And Tor is ready 21.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.926
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.867
Given I shutdown Tails and wait for the computer to power off 1:18.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.874
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.035
And Tor is ready 19.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.807
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.527
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.272
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.400
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.037
And Tor is ready 17.947
Then the Upgrader considers the system as up-to-date 0.342
# 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.993
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.017
After features/support/hooks.rb:320 0.862
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
34.008
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.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 1.479
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 15.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.557
After features/support/hooks.rb:320 1.256
After features/support/hooks.rb:100 0.000