Project Number Date
test_Tails_ISO_stable 5073 05 Sep 2024, 12:30

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:46.197 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:15.663
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.939
When I start Tails from USB drive "old" with network unplugged 1:37.152
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.396
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 7.323
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.466
Before features/support/hooks.rb:269 0.006
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:29.654
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 32.132
And I take note of which tps features are available 1.636
Then a Tails persistence partition exists on USB drive "old" 0.907
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:326 0.211
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.127
Before features/support/hooks.rb:269 0.003
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.783
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.095
When I write some files expected to persist 1.614
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.387
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.326
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.138
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.872
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.734
And I log in to a new session 18.246
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.273
Then the running Tails is installed on USB drive "to_upgrade" 23.253
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.593
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.248
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.253
Then all tps features from the old Tails version are active 1.708
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.475
And the expected persistent files created with the old Tails version are present in the filesystem 1.661
And all persistent directories from the old Tails version have safe access rights 2.613
After features/support/hooks.rb:326 0.897
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:59.956
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 11.568
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.078
And Tor is ready 21.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.512
Given I shutdown Tails and wait for the computer to power off 8.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.173
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.199
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# 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.250
When the network is plugged 0.069
And Tor is ready 17.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.305
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.541
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.085
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.252
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.264
And Tor is ready 45.204
Then the Upgrader considers the system as up-to-date 0.339
# 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 13.943
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.021
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
34.863
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.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.096
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 16.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.296
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.000