Project Number Date
test_Tails_ISO_stable 4900 18 Jun 2024, 19:58

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:0.445 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:16.170
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.195
When I start Tails from USB drive "old" with network unplugged 1:40.671
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:320 3.693
After features/support/hooks.rb:100 0.012
Tags: @product
2:5.964
Before features/support/hooks.rb:269 0.009
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:23.071
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.519
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:320 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.594
Before features/support/hooks.rb:269 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.249
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.144
When I write some files expected to persist 1.693
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.397
And I shutdown Tails and wait for the computer to power off 4.391
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.210
After features/support/hooks.rb:320 0.140
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.839
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.968
And I log in to a new session 19.106
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.610
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.243
Then the running Tails is installed on USB drive "to_upgrade" 22.986
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:320 1.021
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.285
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.984
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.357
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.508
After features/support/hooks.rb:320 0.767
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:17.391
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 10.289
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.051
And Tor is ready 19.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.260
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.428
Given I shutdown Tails and wait for the computer to power off 8.689
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.294
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.430
# 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.265
When the network is plugged 0.035
And Tor is ready 16.430
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.616
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.725
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.041
And Tor is ready 16.452
Then the Upgrader considers the system as up-to-date 10.722
# 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.728
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.859
After features/support/hooks.rb:320 0.702
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.199
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.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.748
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 19.728
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.335
After features/support/hooks.rb:320 0.686
After features/support/hooks.rb:100 0.000