Project Number Date
test_Tails_ISO_devel 3566 29 Oct 2024, 12:46

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:48.667 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
3:18.371
Before features/support/hooks.rb:269 0.004
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 1:21.758
When I start Tails from USB drive "old" with network unplugged 1:50.402
Then the boot device has safe access rights 3.562
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.429
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:326 8.895
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.289
Before features/support/hooks.rb:269 0.008
Given a computer 0.370
And I start Tails from USB drive "old" with network unplugged and I login 1:30.787
Then Tails is running from USB drive "old" 0.444
And I create a persistent partition 33.657
And I take note of which tps features are available 2.043
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 9.113
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.052
Before features/support/hooks.rb:269 0.008
Given a computer 0.369
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.858
Then Tails is running from USB drive "old" 0.565
And all tps features are active 3.117
When I write some files expected to persist 1.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.799
And I take note of which tps features are available 0.641
And I shutdown Tails and wait for the computer to power off 4.530
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.484
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.411
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 45.665
And I log in to a new session 22.496
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.103
And I plug USB drive "to_upgrade" 2.484
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.235
Then the running Tails is installed on USB drive "to_upgrade" 26.981
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 7.645
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.831
Before features/support/hooks.rb:269 0.008
Given a computer 0.386
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.256
Then all tps features from the old Tails version are active 2.640
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.743
And the expected persistent files created with the old Tails version are present in the filesystem 1.787
And all persistent directories from the old Tails version have safe access rights 2.696
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
6:41.035
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 15.165
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.604
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
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.500
When the network is plugged 0.093
And Tor is ready 21.846
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.839
Given I shutdown Tails and wait for the computer to power off 11.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.033
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# 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.391
When the network is plugged 0.087
And Tor is ready 20.881
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.327
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.516
Given I shutdown Tails and wait for the computer to power off 4.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.435
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.073
And Tor is ready 20.283
Then the Upgrader considers the system as up-to-date 0.320
# 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.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.166
After features/support/hooks.rb:326 0.824
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
41.675
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.952
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.806
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 22.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.518
After features/support/hooks.rb:326 2.015
After features/support/hooks.rb:100 0.000