Project Number Date
test_Tails_ISO_devel 3526 01 Oct 2024, 12:42

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:13.943 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:3.172
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.340
When I start Tails from USB drive "old" with network unplugged 1:27.452
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:326 7.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.052
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:23.017
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.647
And I take note of which tps features are available 1.617
Then a Tails persistence partition exists on USB drive "old" 0.722
And I shutdown Tails and wait for the computer to power off 8.498
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.814
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 with persistence enabled 2:25.111
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.207
When I write some files expected to persist 1.775
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.529
And all persistent directories from the old Tails version have safe access rights 2.688
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 4.621
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.463
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.588
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.528
And I log in to a new session 18.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.341
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.728
Then the running Tails is installed on USB drive "to_upgrade" 17.542
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:326 1.971
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.414
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.157
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.106
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.729
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.817
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 11.764
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.084
And Tor is ready 20.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.078
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.374
Given I shutdown Tails and wait for the computer to power off 11.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.177
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.313
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.308
When the network is plugged 0.077
And Tor is ready 47.317
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.836
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.038
Then Tails is running version 6.3~testoverlayfs 0.037
And all tps features are active 2.023
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.088
And Tor is ready 19.190
Then the Upgrader considers the system as up-to-date 0.311
# 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 13.788
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.014
After features/support/hooks.rb:326 0.796
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.083
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.234
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 16.341
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000