Project Number Date
test_Tails_ISO_devel 3687 12 Feb 2025, 15:30

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:46.098 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:1.214
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.189
When I start Tails from USB drive "old" with network unplugged 1:25.445
Then the boot device has safe access rights 3.140
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.401
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 11.289
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.122
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:34.254
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.724
And I take note of which tps features are available 1.345
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:326 0.282
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.824
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.376
Then Tails is running from USB drive "old" 0.632
And all tps features are active 1.906
When I write some files expected to persist 2.344
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.946
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.202
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.173
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.263
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.882
And I log in to a new session 18.539
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.012
Then the running Tails is installed on USB drive "to_upgrade" 19.264
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.213
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.401
Before features/support/hooks.rb:269 0.006
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.044
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.217
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.420
After features/support/hooks.rb:326 0.970
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:9.353
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.677
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
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.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.065
And Tor is ready 18.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.215
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.019
Given I shutdown Tails and wait for the computer to power off 8.692
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.278
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.972
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.268
When the network is plugged 0.069
And Tor is ready 18.638
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.882
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.692
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.073
And Tor is ready 18.527
Then the Upgrader considers the system as up-to-date 0.386
# 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.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.903
After features/support/hooks.rb:326 0.867
After features/support/hooks.rb:100 0.120
Tags: @product @automatic_upgrade
32.919
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 16.858
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.061
After features/support/hooks.rb:326 1.092
After features/support/hooks.rb:100 0.000