Project Number Date
test_Tails_ISO_stable 4889 13 Jun 2024, 14:03

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:24.612 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:10.937
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 34.327
When I start Tails from USB drive "old" with network unplugged 1:31.084
Then the boot device has safe access rights 3.145
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:320 3.734
After features/support/hooks.rb:100 0.013
Tags: @product
2:17.056
Before features/support/hooks.rb:269 0.009
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:27.477
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 35.628
And I take note of which tps features are available 3.582
Then a Tails persistence partition exists on USB drive "old" 1.061
And I shutdown Tails and wait for the computer to power off 8.650
After features/support/hooks.rb:320 0.188
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.701
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:21.931
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.145
When I write some files expected to persist 1.808
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.880
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.524
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.593
After features/support/hooks.rb:320 0.161
After features/support/hooks.rb:100 0.013
Tags: @product
2:25.442
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.140
And I log in to a new session 16.436
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.336
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.084
Then the running Tails is installed on USB drive "to_upgrade" 17.519
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:320 3.705
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.411
Before features/support/hooks.rb:269 0.008
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.323
Then all tps features from the old Tails version are active 2.889
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.542
And the expected persistent files created with the old Tails version are present in the filesystem 1.441
And all persistent directories from the old Tails version have safe access rights 2.516
After features/support/hooks.rb:320 0.736
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:40.668
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 11.980
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.039
And Tor is ready 19.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.712
Given I shutdown Tails and wait for the computer to power off 8.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.651
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.479
And the file system changes introduced in version 6.2~testoverlayfs are present 0.376
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.476
# 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.304
When the network is plugged 0.043
And Tor is ready 21.828
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.769
Given I shutdown Tails and wait for the computer to power off 4.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.127
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 3.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.042
And Tor is ready 18.813
Then the Upgrader considers the system as up-to-date 0.380
# 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 15.357
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.318
After features/support/hooks.rb:320 0.877
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
39.393
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.868
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.186
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 20.640
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.241
After features/support/hooks.rb:320 0.732
After features/support/hooks.rb:100 0.000