Project Number Date
test_Tails_ISO_devel 3587 15 Nov 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 19:3.226 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:5.628
Before features/support/hooks.rb:269 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.618
When I start Tails from USB drive "old" with network unplugged 1:29.597
Then the boot device has safe access rights 3.136
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.572
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.072
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:22.167
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.609
And I take note of which tps features are available 1.448
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.514
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.843
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.327
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.922
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.609
And I take note of which tps features are available 0.395
And I shutdown Tails and wait for the computer to power off 4.302
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.505
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.927
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 11.482
And I log in to a new session 18.363
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.771
And I plug USB drive "to_upgrade" 2.915
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.151
Then the running Tails is installed on USB drive "to_upgrade" 23.819
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.643
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.773
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.319
Then all tps features from the old Tails version are active 1.576
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.413
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:43.110
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 30.384
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.062
And Tor is ready 20.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.534
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.894
Given I shutdown Tails and wait for the computer to power off 8.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.209
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.282
When the network is plugged 0.072
And Tor is ready 20.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.043
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.892
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.000
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.294
When the network is plugged 0.106
And Tor is ready 19.484
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 15.433
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.977
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.870
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 9.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.798
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.498
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.000