Project Number Date
test_Tails_ISO_stable 5604 28 Apr 2025, 20:36

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:48.543 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:25.204
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.251
When I start Tails from USB drive "old" with network unplugged 1:48.426
Then the boot device has safe access rights 3.171
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.793
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.208
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:31.740
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 31.900
And I take note of which tps features are available 2.500
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 8.677
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.965
Then Tails is running from USB drive "old" 0.511
And all tps features are active 2.422
When I write some files expected to persist 1.889
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.523
And I take note of which tps features are available 0.665
And I shutdown Tails and wait for the computer to power off 6.701
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.472
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.423
And I log in to a new session 21.465
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.885
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.953
Then the running Tails is installed on USB drive "to_upgrade" 27.864
And I unplug USB drive "to_upgrade" 0.308
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 7.226
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.813
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.998
Then all tps features from the old Tails version are active 2.194
And Tails is running from USB drive "to_upgrade" 0.453
And the boot device has safe access rights 4.067
And the expected persistent files created with the old Tails version are present in the filesystem 1.774
And all persistent directories from the old Tails version have safe access rights 3.094
After features/support/hooks.rb:330 1.399
After features/support/hooks.rb:100 0.010
7:1.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.251
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.073
And Tor is ready 24.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.841
Given I shutdown Tails and wait for the computer to power off 13.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.645
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.453
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.397
# 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.289
When the network is plugged 0.077
And Tor is ready 21.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.695
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.636
Given I shutdown Tails and wait for the computer to power off 4.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.226
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.577
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.095
And Tor is ready 18.668
Then the Upgrader considers the system as up-to-date 0.372
# 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.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.517
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.020
40.247
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 with a persistent partition enabled and logged in 11.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.145
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 19.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.115
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.000