Project Number Date
test_Tails_ISO_feature-arti 96 23 Jun 2025, 19:31

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:25.070 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:7.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 29.091
When I start Tails from USB drive "old" with network unplugged 1:32.614
Then the boot device has safe access rights 3.616
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.712
After features/support/hooks.rb:100 0.020
Tags: @product
2:10.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:30.419
Then Tails is running from USB drive "old" 0.512
And I create a persistent partition 30.002
And I take note of which tps features are available 2.231
Then a Tails persistence partition exists on USB drive "old" 0.693
And I shutdown Tails and wait for the computer to power off 6.814
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.326
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.291
Then Tails is running from USB drive "old" 0.424
And all tps features are active 2.343
When I write some files expected to persist 1.803
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.580
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.541
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.927
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.404
And I log in to a new session 19.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 2.596
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.888
Then the running Tails is installed on USB drive "to_upgrade" 27.539
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.272
After features/support/hooks.rb:330 1.844
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.901
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.273
Then all tps features from the old Tails version are active 2.064
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.964
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.563
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.077
Tags: @product @automatic_upgrade
7:17.182
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 13.604
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.474
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 0.086
And Tor is ready 25.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.884
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.772
Given I shutdown Tails and wait for the computer to power off 12.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.611
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.751
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.117
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.374
# 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.293
When the network is plugged 0.089
And Tor is ready 19.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.164
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.301
Given I shutdown Tails and wait for the computer to power off 6.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.657
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.780
And the file system changes introduced in version 6.3~testoverlayfs are present 0.631
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.074
And Tor is ready 21.010
Then the Upgrader considers the system as up-to-date 0.317
# 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 18.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.893
After features/support/hooks.rb:330 0.766
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.590
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 10.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.742
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 21.700
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.724
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.000