Project Number Date
test_Tails_ISO_devel 3847 01 Jun 2025, 13:18

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 19:51.548 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:15.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 33.076
When I start Tails from USB drive "old" with network unplugged 1:37.239
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 9.971
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:30.568
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.645
And I take note of which tps features are available 1.887
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.736
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.764
Then Tails is running from USB drive "old" 1.039
And all tps features are active 2.437
When I write some files expected to persist 2.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.581
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.983
And I take note of which tps features are available 0.568
And I shutdown Tails and wait for the computer to power off 6.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.880
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.007
Tags: @product
2:38.034
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 without a persistent partition and stopped at Tails Greeter's login screen 11.302
And I log in to a new session 20.768
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.473
Then the running Tails is installed on USB drive "to_upgrade" 24.975
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 2.047
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.540
Then all tps features from the old Tails version are active 2.204
And Tails is running from USB drive "to_upgrade" 0.485
And the boot device has safe access rights 3.586
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:330 1.524
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:43.635
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 11.917
And no SquashFS delta is installed 0.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.714
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.963
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.576
When the network is plugged 0.174
And Tor is ready 19.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.943
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.267
Given I shutdown Tails and wait for the computer to power off 11.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.807
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.540
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.323
When the network is plugged 0.102
And Tor is ready 18.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.570
Given I shutdown Tails and wait for the computer to power off 6.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.649
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.086
And Tor is ready 19.534
Then the Upgrader considers the system as up-to-date 0.321
# 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.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.186
After features/support/hooks.rb:330 0.813
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
36.545
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.341
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.118
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 18.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.945
After features/support/hooks.rb:330 0.784
After features/support/hooks.rb:100 0.000