Project Number Date
test_Tails_ISO_stable 5650 15 May 2025, 22:24

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 20:13.284 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:23.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.392
When I start Tails from USB drive "old" with network unplugged 1:44.687
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.397
And I unplug USB drive "old" 0.565
After features/support/hooks.rb:330 7.865
After features/support/hooks.rb:100 0.012
Tags: @product
2:12.861
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:27.697
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.679
And I take note of which tps features are available 1.825
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 10.368
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.060
Then Tails is running from USB drive "old" 0.309
And all tps features are active 1.991
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
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.308
And I take note of which tps features are available 0.615
And I shutdown Tails and wait for the computer to power off 4.670
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.599
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.883
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.405
And I log in to a new session 18.175
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.561
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.033
Then the running Tails is installed on USB drive "to_upgrade" 23.824
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 1.725
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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:7.632
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.910
And the expected persistent files created with the old Tails version are present in the filesystem 1.443
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:330 1.250
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:10.778
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 11.603
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.083
And Tor is ready 22.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.883
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.672
Given I shutdown Tails and wait for the computer to power off 11.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.453
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.268
When the network is plugged 0.072
And Tor is ready 18.254
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.099
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.938
Given I shutdown Tails and wait for the computer to power off 6.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.985
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.070
And Tor is ready 19.051
Then the Upgrader considers the system as up-to-date 10.855
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.522
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
44.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.789
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the signing key used by the Upgrader is outdated 0.158
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 23.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.053
After features/support/hooks.rb:330 0.643
After features/support/hooks.rb:100 0.000