Project Number Date
test_Tails_ISO_devel 3560 24 Oct 2024, 12:43

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 19:56.663 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:10.056
Before features/support/hooks.rb:269 0.008
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.611
When I start Tails from USB drive "old" with network unplugged 1:33.847
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.026
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.825
Before features/support/hooks.rb:269 0.027
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:20.507
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 36.891
And I take note of which tps features are available 1.663
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.399
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.012
Tags: @product
3:10.537
Before features/support/hooks.rb:269 0.016
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.846
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.090
When I write some files expected to persist 2.097
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.413
And all persistence configuration files have safe access rights 0.548
And all persistent directories from the old Tails version have safe access rights 2.632
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.348
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.567
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.857
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 13.716
And I log in to a new session 23.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.811
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.189
Then the running Tails is installed on USB drive "to_upgrade" 23.619
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.011
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.086
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.584
Then all tps features from the old Tails version are active 1.781
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.112
And the expected persistent files created with the old Tails version are present in the filesystem 1.645
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
6:39.358
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 12.852
And no SquashFS delta is installed 0.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.062
And Tor is ready 18.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.737
Given I shutdown Tails and wait for the computer to power off 10.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.369
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.454
And the file system changes introduced in version 6.2~testoverlayfs are present 0.485
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.289
When the network is plugged 0.070
And Tor is ready 16.601
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.358
Given I shutdown Tails and wait for the computer to power off 6.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.312
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.412
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.379
When the network is plugged 0.074
And Tor is ready 21.707
Then the Upgrader considers the system as up-to-date 0.343
# 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 14.169
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.035
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
52.939
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 26.355
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
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.942
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.762
After features/support/hooks.rb:326 1.668
After features/support/hooks.rb:100 0.000