Project Number Date
test_Tails_ISO_stable 5340 17 Dec 2024, 08:35

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:24.161 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.649
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.614
When I start Tails from USB drive "old" with network unplugged 1:28.500
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.258
After features/support/hooks.rb:326 3.839
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.481
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:26.716
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.620
And I take note of which tps features are available 1.394
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.316
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.017
Tags: @product
2:46.964
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.327
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.021
When I write some files expected to persist 1.656
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 3.061
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.286
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.974
After features/support/hooks.rb:326 0.101
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.462
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.019
And I log in to a new session 19.302
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.666
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.371
Then the running Tails is installed on USB drive "to_upgrade" 18.222
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 3.550
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.724
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.041
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.579
And the expected persistent files created with the old Tails version are present in the filesystem 1.518
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.904
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.096
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.089
And Tor is ready 22.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.343
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.444
Given I shutdown Tails and wait for the computer to power off 8.829
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.458
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.447
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.354
When the network is plugged 0.089
And Tor is ready 20.180
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.377
Given I shutdown Tails and wait for the computer to power off 4.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.581
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.414
When the network is plugged 0.088
And Tor is ready 18.078
Then the Upgrader considers the system as up-to-date 0.348
# 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.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.954
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
1:11.973
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 23.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.742
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 47.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.586
After features/support/hooks.rb:326 0.614
After features/support/hooks.rb:100 0.000