Project Number Date
test_Tails_ISO_devel 3821 19 May 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 18:59.379 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:6.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.108
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.700
When I start Tails from USB drive "old" with network unplugged 1:30.239
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:330 8.336
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:25.071
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 30.848
And I take note of which tps features are available 2.071
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 8.318
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.012
Tags: @product
2:55.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.035
Then Tails is running from USB drive "old" 0.403
And all tps features are active 1.961
When I write some files expected to persist 1.522
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.385
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.507
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.927
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 without a persistent partition and stopped at Tails Greeter's login screen 11.469
And I log in to a new session 18.829
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.853
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.959
Then the running Tails is installed on USB drive "to_upgrade" 19.983
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 0.817
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.230
Then all tps features from the old Tails version are active 1.668
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.355
And all persistent directories from the old Tails version have safe access rights 2.520
After features/support/hooks.rb:330 1.106
After features/support/hooks.rb:100 0.008
6:29.250
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.114
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.441
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.436
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.066
And Tor is ready 17.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.529
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.554
Given I shutdown Tails and wait for the computer to power off 8.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.308
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.178
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.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.303
When the network is plugged 0.059
And Tor is ready 17.565
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.657
Given I shutdown Tails and wait for the computer to power off 4.338
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.140
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.072
And Tor is ready 15.573
Then the Upgrader considers the system as up-to-date 0.336
# 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.747
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.746
After features/support/hooks.rb:330 0.676
After features/support/hooks.rb:100 0.019
33.855
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 9.990
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.155
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 16.734
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.474
After features/support/hooks.rb:330 0.695
After features/support/hooks.rb:100 0.000