Project Number Date
test_Tails_ISO_devel 3550 16 Oct 2024, 12: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 21:12.565 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:15.274
Before features/support/hooks.rb:269 0.007
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.792
When I start Tails from USB drive "old" with network unplugged 1:37.082
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.543
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.402
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:22.342
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 32.120
And I take note of which tps features are available 1.991
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 6.429
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.379
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.853
Then Tails is running from USB drive "old" 0.936
And all tps features are active 2.146
When I write some files expected to persist 2.030
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 3.121
And I take note of which tps features are available 0.708
And I shutdown Tails and wait for the computer to power off 6.805
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.847
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.621
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 30.634
And I log in to a new session 19.078
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.109
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.348
Then the running Tails is installed on USB drive "to_upgrade" 31.486
And I unplug USB drive "to_upgrade" 0.292
And I unplug USB drive "__internal" 0.290
After features/support/hooks.rb:326 2.430
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.919
Before features/support/hooks.rb:269 0.016
Given a computer 0.339
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.861
Then all tps features from the old Tails version are active 2.638
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.777
And all persistent directories from the old Tails version have safe access rights 2.565
After features/support/hooks.rb:326 0.738
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:34.046
Before features/support/hooks.rb:269 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.419
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.536
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.622
When the network is plugged 0.099
And Tor is ready 21.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.085
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.410
Given I shutdown Tails and wait for the computer to power off 11.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.867
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.356
And the file system changes introduced in version 6.2~testoverlayfs are present 0.398
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.462
# 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.386
When the network is plugged 0.097
And Tor is ready 22.073
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.850
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.777
Given I shutdown Tails and wait for the computer to power off 6.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.847
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.442
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.437
When the network is plugged 0.164
And Tor is ready 18.028
Then the Upgrader considers the system as up-to-date 0.333
# 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.012
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.620
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.920
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 14.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 1.008
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 18.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.526
After features/support/hooks.rb:326 1.960
After features/support/hooks.rb:100 0.000