Project Number Date
test_Tails_ISO_devel 3719 04 Mar 2025, 13:27

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:58.964 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:42.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.413
And I create a 7200 MiB disk named "old" 0.087
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 58.846
When I start Tails from USB drive "old" with network unplugged 1:37.238
Then the boot device has safe access rights 3.708
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.305
After features/support/hooks.rb:330 11.086
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.345
And I start Tails from USB drive "old" with network unplugged and I login 1:28.782
Then Tails is running from USB drive "old" 0.483
And I create a persistent partition 32.402
And I take note of which tps features are available 1.955
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.674
After features/support/hooks.rb:330 0.267
After features/support/hooks.rb:100 0.013
Tags: @product
3:2.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.597
Then Tails is running from USB drive "old" 0.463
And all tps features are active 2.083
When I write some files expected to persist 1.798
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.525
And all persistent directories from the old Tails version have safe access rights 2.861
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.313
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.934
After features/support/hooks.rb:330 0.123
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.212
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 11.301
And I log in to a new session 22.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.175
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.066
Then the running Tails is installed on USB drive "to_upgrade" 23.812
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:330 2.317
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.173
Then all tps features from the old Tails version are active 1.908
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 4.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.652
And all persistent directories from the old Tails version have safe access rights 2.720
After features/support/hooks.rb:330 1.192
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
7:18.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.334
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
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 0.662
When the network is plugged 0.086
And Tor is ready 24.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.392
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.723
Given I shutdown Tails and wait for the computer to power off 12.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.050
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.824
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
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.388
# 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.386
When the network is plugged 0.110
And Tor is ready 22.484
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.727
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.558
Given I shutdown Tails and wait for the computer to power off 4.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.731
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.754
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.084
And Tor is ready 19.820
Then the Upgrader considers the system as up-to-date 0.403
# 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 17.866
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.027
After features/support/hooks.rb:330 1.075
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
45.553
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 with a persistent partition enabled and logged in 13.616
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.130
And Tor is ready 22.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.396
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.000