Project Number Date
test_Tails_ISO_stable 5362 31 Dec 2024, 12:20

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:42.340 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:6.078
Before features/support/hooks.rb:269 0.003
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.734
When I start Tails from USB drive "old" with network unplugged 1:29.981
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.250
After features/support/hooks.rb:326 7.271
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.739
Before features/support/hooks.rb:269 0.004
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:22.733
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 31.475
And I take note of which tps features are available 1.507
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.605
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.506
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.180
Then Tails is running from USB drive "old" 1.225
And all tps features are active 2.106
When I write some files expected to persist 1.703
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 3.660
And I take note of which tps features are available 0.573
And I shutdown Tails and wait for the computer to power off 4.262
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.875
After features/support/hooks.rb:326 0.083
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.537
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.768
And I log in to a new session 18.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.634
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.918
Then the running Tails is installed on USB drive "to_upgrade" 21.718
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.404
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.770
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.804
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.143
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.342
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:22.723
Before features/support/hooks.rb:269 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.059
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
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.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.074
And Tor is ready 25.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.308
Given I shutdown Tails and wait for the computer to power off 8.702
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.230
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.261
When the network is plugged 0.060
And Tor is ready 16.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.293
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.485
Given I shutdown Tails and wait for the computer to power off 4.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.132
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.663
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.064
And Tor is ready 17.451
Then the Upgrader considers the system as up-to-date 0.305
# 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 16.233
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.610
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.984
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.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
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 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.004
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.379
After features/support/hooks.rb:326 1.491
After features/support/hooks.rb:100 0.000