Project Number Date
test_Tails_ISO_stable 5419 27 Jan 2025, 12:51

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 22:2.741 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
1:57.689
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.205
When I start Tails from USB drive "old" with network unplugged 1:22.100
Then the boot device has safe access rights 2.973
And Tails is running from USB drive "old" 0.404
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.555
After features/support/hooks.rb:100 0.022
Tags: @product
2:11.949
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:24.315
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 35.309
And I take note of which tps features are available 3.334
Then a Tails persistence partition exists on USB drive "old" 0.986
And I shutdown Tails and wait for the computer to power off 7.364
After features/support/hooks.rb:326 0.253
After features/support/hooks.rb:100 0.014
Tags: @product
2:57.484
Before features/support/hooks.rb:269 0.006
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.722
Then Tails is running from USB drive "old" 0.690
And all tps features are active 2.357
When I write some files expected to persist 2.446
# 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.385
And all persistent directories from the old Tails version have safe access rights 2.749
And I take note of which tps features are available 0.610
And I shutdown Tails and wait for the computer to power off 4.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.656
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.191
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.390
And I log in to a new session 19.022
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.415
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.187
Then the running Tails is installed on USB drive "to_upgrade" 22.299
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.657
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.076
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.043
Then all tps features from the old Tails version are active 1.851
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.344
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.807
After features/support/hooks.rb:326 1.104
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
8:47.546
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.983
And no SquashFS delta is installed 0.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.086
And Tor is ready 24.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.989
Given I shutdown Tails and wait for the computer to power off 1:17.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.162
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.648
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.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.301
When the network is plugged 0.102
And Tor is ready 16.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.889
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.085
Given I shutdown Tails and wait for the computer to power off 4.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.605
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.638
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.083
And Tor is ready 49.182
Then the Upgrader considers the system as up-to-date 0.376
# 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 16.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.209
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
1:11.803
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 18.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.090
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.161
And Tor is ready 51.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.697
After features/support/hooks.rb:326 1.203
After features/support/hooks.rb:100 0.000