Project Number Date
test_Tails_ISO_stable 5094 11 Sep 2024, 17: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 19:35.006 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:12.274
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 37.328
When I start Tails from USB drive "old" with network unplugged 1:29.356
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.012
Tags: @product
2:12.376
Before features/support/hooks.rb:269 0.009
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login 1:26.198
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 34.295
And I take note of which tps features are available 1.655
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.704
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.682
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.388
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.122
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.715
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.742
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.406
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.255
And I log in to a new session 21.030
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.974
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.842
Then the running Tails is installed on USB drive "to_upgrade" 20.479
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.279
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.348
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.296
Then all tps features from the old Tails version are active 1.767
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.452
And all persistent directories from the old Tails version have safe access rights 2.657
After features/support/hooks.rb:326 0.932
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.732
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.443
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.070
And Tor is ready 20.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.615
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.835
Given I shutdown Tails and wait for the computer to power off 8.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.012
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.473
# 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.293
When the network is plugged 0.071
And Tor is ready 17.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.320
Given I shutdown Tails and wait for the computer to power off 4.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.765
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.152
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.122
# 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.528
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.095
And Tor is ready 19.104
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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.186
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 9.990
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.018
But a current signing key is available on our website 0.000
When the network is plugged 0.141
And Tor is ready 16.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.735
After features/support/hooks.rb:326 1.035
After features/support/hooks.rb:100 0.000