Project Number Date
test_Tails_ISO_stable 5516 15 Mar 2025, 13:23

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 18:24.122 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:2.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.141
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 30.733
When I start Tails from USB drive "old" with network unplugged 1:26.532
Then the boot device has safe access rights 2.799
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 6.687
After features/support/hooks.rb:100 0.006
Tags: @product
2:1.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.142
And I start Tails from USB drive "old" with network unplugged and I login 1:20.821
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 29.990
And I take note of which tps features are available 1.398
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.125
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.006
Tags: @product
2:46.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.644
Then Tails is running from USB drive "old" 0.394
And all tps features are active 1.947
When I write some files expected to persist 1.932
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.215
And I take note of which tps features are available 0.715
And I shutdown Tails and wait for the computer to power off 4.130
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.996
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.006
Tags: @product
2:31.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.258
And I log in to a new session 20.078
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.975
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.692
Then the running Tails is installed on USB drive "to_upgrade" 22.366
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 2.422
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.152
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.685
Then all tps features from the old Tails version are active 1.466
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.033
And the expected persistent files created with the old Tails version are present in the filesystem 1.599
And all persistent directories from the old Tails version have safe access rights 2.528
After features/support/hooks.rb:330 1.014
After features/support/hooks.rb:100 0.006
6:14.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.640
And no SquashFS delta is installed 0.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.085
And Tor is ready 20.189
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.489
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.955
Given I shutdown Tails and wait for the computer to power off 8.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.454
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.061
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.321
When the network is plugged 0.073
And Tor is ready 19.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.029
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.516
Given I shutdown Tails and wait for the computer to power off 4.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.620
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.853
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.077
And Tor is ready 16.952
Then the Upgrader considers the system as up-to-date 0.314
# 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.555
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:330 0.698
After features/support/hooks.rb:100 0.094
36.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.994
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
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.074
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 22.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.483
After features/support/hooks.rb:330 1.071
After features/support/hooks.rb:100 0.000