Project Number Date
test_Tails_ISO_stable 5595 24 Apr 2025, 15:08

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:23.536 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:40.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.106
When I start Tails from USB drive "old" with network unplugged 2:0.796
Then the boot device has safe access rights 4.072
And Tails is running from USB drive "old" 0.407
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 7.275
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:43.583
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.300
And I take note of which tps features are available 2.580
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 9.703
After features/support/hooks.rb:330 0.275
After features/support/hooks.rb:100 0.013
Tags: @product
3:12.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.761
Then Tails is running from USB drive "old" 1.132
And all tps features are active 6.427
When I write some files expected to persist 1.903
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 3.423
And I take note of which tps features are available 0.985
And I shutdown Tails and wait for the computer to power off 4.524
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.541
After features/support/hooks.rb:330 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.937
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.240
And I log in to a new session 22.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.856
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.293
Then the running Tails is installed on USB drive "to_upgrade" 27.203
And I unplug USB drive "to_upgrade" 0.339
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:330 1.033
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.307
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.815
Then all tps features from the old Tails version are active 1.929
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.538
And all persistent directories from the old Tails version have safe access rights 3.059
After features/support/hooks.rb:330 1.294
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:14.520
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 16.851
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.502
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.010
When the network is plugged 0.077
And Tor is ready 22.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.560
Given I shutdown Tails and wait for the computer to power off 9.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.833
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.300
When the network is plugged 0.072
And Tor is ready 16.562
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.023
Given I shutdown Tails and wait for the computer to power off 4.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.989
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.312
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.074
And Tor is ready 47.985
Then the Upgrader considers the system as up-to-date 0.394
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.764
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
41.474
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 10.949
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.225
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.000