Project Number Date
test_Tails_ISO_devel 3606 08 Dec 2024, 12:34

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:9.827 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:18.758
Before features/support/hooks.rb:269 0.007
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.601
When I start Tails from USB drive "old" with network unplugged 1:43.490
Then the boot device has safe access rights 3.269
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 9.757
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.280
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:27.320
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.259
And I take note of which tps features are available 1.951
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.335
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.546
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.570
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.234
When I write some files expected to persist 1.766
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.597
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.467
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.325
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.438
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.482
And I log in to a new session 19.047
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.751
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.962
Then the running Tails is installed on USB drive "to_upgrade" 19.372
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.393
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.890
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.665
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.067
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.332
After features/support/hooks.rb:326 0.878
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:0.501
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 13.154
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
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.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.077
And Tor is ready 23.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.173
Given I shutdown Tails and wait for the computer to power off 10.970
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.823
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.475
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.272
When the network is plugged 0.068
And Tor is ready 17.273
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.703
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.075
Given I shutdown Tails and wait for the computer to power off 4.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.180
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.954
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.409
When the network is plugged 0.070
And Tor is ready 18.092
Then the Upgrader considers the system as up-to-date 10.868
# 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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.411
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 10.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.888
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 23.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.095
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.000