Project Number Date
test_Tails_ISO_stable 5098 13 Sep 2024, 12:56

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:55.711 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.800
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 33.339
When I start Tails from USB drive "old" with network unplugged 1:34.938
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 7.740
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.077
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:24.265
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.683
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.214
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.007
Tags: @product
3:8.879
Before features/support/hooks.rb:269 0.003
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.317
Then Tails is running from USB drive "old" 0.374
And all tps features are active 2.062
When I write some files expected to persist 2.015
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.591
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.462
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.694
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.275
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.625
And I log in to a new session 18.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.744
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.342
Then the running Tails is installed on USB drive "to_upgrade" 21.677
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 7.521
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.930
Before features/support/hooks.rb:269 0.005
Given a computer 1.913
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.607
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.543
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.469
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.471
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 12.843
And no SquashFS delta is installed 0.247
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.535
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.602
When the network is plugged 0.092
And Tor is ready 24.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.929
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.408
Given I shutdown Tails and wait for the computer to power off 8.961
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.840
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.294
When the network is plugged 0.067
And Tor is ready 17.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.663
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.532
Given I shutdown Tails and wait for the computer to power off 4.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.528
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.087
And Tor is ready 18.557
Then the Upgrader considers the system as up-to-date 0.352
# 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.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.165
After features/support/hooks.rb:326 0.973
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.276
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.806
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 21.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.467
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.000