Project Number Date
test_Tails_ISO_stable 5114 24 Sep 2024, 12:06

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 18:30.477 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
1:59.454
Before features/support/hooks.rb:269 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.522
When I start Tails from USB drive "old" with network unplugged 1:23.954
Then the boot device has safe access rights 2.787
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.524
After features/support/hooks.rb:100 0.083
Tags: @product
2:3.609
Before features/support/hooks.rb:269 0.005
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:21.002
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 31.286
And I take note of which tps features are available 1.489
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.612
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.313
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.354
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.858
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.638
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.284
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.111
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.024
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 10.709
And I log in to a new session 18.238
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.814
Then the running Tails is installed on USB drive "to_upgrade" 16.774
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.000
Tags: @product
1:58.210
Before features/support/hooks.rb:269 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.464
Then all tps features from the old Tails version are active 1.535
And Tails is running from USB drive "to_upgrade" 0.422
And the boot device has safe access rights 3.092
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:49.383
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.158
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.071
And Tor is ready 51.473
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.556
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.381
Given I shutdown Tails and wait for the computer to power off 8.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.942
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.937
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.296
When the network is plugged 0.073
And Tor is ready 18.971
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.265
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.672
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.216
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.273
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.100
And Tor is ready 16.811
Then the Upgrader considers the system as up-to-date 10.736
# 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.916
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.481
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.732
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.575
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.305
After features/support/hooks.rb:326 0.888
After features/support/hooks.rb:100 0.000