Project Number Date
test_Tails_ISO_stable 5517 16 Mar 2025, 13:00

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 21:42.631 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:13.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.086
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.231
When I start Tails from USB drive "old" with network unplugged 1:35.840
Then the boot device has safe access rights 3.287
And Tails is running from USB drive "old" 0.429
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.506
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:32.040
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 31.462
And I take note of which tps features are available 1.968
Then a Tails persistence partition exists on USB drive "old" 0.914
And I shutdown Tails and wait for the computer to power off 8.653
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.697
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.446
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.176
When I write some files expected to persist 1.930
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 3.160
And I take note of which tps features are available 0.527
And I shutdown Tails and wait for the computer to power off 6.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.805
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 12.244
And I log in to a new session 23.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.489
Then the running Tails is installed on USB drive "to_upgrade" 21.725
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 3.684
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.022
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.271
And the expected persistent files created with the old Tails version are present in the filesystem 1.694
And all persistent directories from the old Tails version have safe access rights 3.677
After features/support/hooks.rb:330 1.793
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
8:8.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.692
And no SquashFS delta is installed 1.247
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.583
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.417
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.099
And Tor is ready 20.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.216
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.296
Given I shutdown Tails and wait for the computer to power off 1:26.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.667
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.277
When the network is plugged 0.068
And Tor is ready 20.748
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.552
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.803
Given I shutdown Tails and wait for the computer to power off 4.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.549
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.363
And the file system changes introduced in version 6.3~testoverlayfs are present 0.586
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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.367
When the network is plugged 0.081
And Tor is ready 18.661
Then the Upgrader considers the system as up-to-date 0.316
# 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.421
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.938
After features/support/hooks.rb:330 0.835
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
1:2.551
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 47.770
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.740
After features/support/hooks.rb:330 0.793
After features/support/hooks.rb:100 0.000