Project Number Date
test_Tails_ISO_stable 4921 08 Jul 2024, 22:05

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 20:2.102 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:45.102
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.293
When I start Tails from USB drive "old" with network unplugged 2:8.206
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 9.902
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.393
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:27.755
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 31.902
And I take note of which tps features are available 1.832
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 10.462
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.624
Before features/support/hooks.rb:269 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.516
Then Tails is running from USB drive "old" 0.408
And all tps features are active 2.500
When I write some files expected to persist 2.182
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.549
And all persistent directories from the old Tails version have safe access rights 2.823
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.132
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.507
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.695
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.667
And I log in to a new session 18.604
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.462
Then the running Tails is installed on USB drive "to_upgrade" 22.570
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.974
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.798
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.161
Then all tps features from the old Tails version are active 1.822
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.260
And the expected persistent files created with the old Tails version are present in the filesystem 1.644
And all persistent directories from the old Tails version have safe access rights 2.353
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:37.861
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 10.365
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.077
And Tor is ready 18.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.253
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.372
Given I shutdown Tails and wait for the computer to power off 8.827
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.453
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.283
When the network is plugged 0.043
And Tor is ready 20.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.620
Given I shutdown Tails and wait for the computer to power off 6.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.206
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.317
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.043
And Tor is ready 19.659
Then the Upgrader considers the system as up-to-date 0.352
# 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.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.140
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
35.625
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.918
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 17.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.531
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000