Project Number Date
test_Tails_ISO_stable 5619 01 May 2025, 08:54

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:42.808 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:0.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.381
When I start Tails from USB drive "old" with network unplugged 1:25.892
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 7.053
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:20.989
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.201
And I take note of which tps features are available 1.671
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 8.463
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.700
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.869
When I write some files expected to persist 1.778
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.417
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.322
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.854
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.693
And I log in to a new session 18.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.450
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.000
Then the running Tails is installed on USB drive "to_upgrade" 27.586
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 1.830
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.582
Then all tps features from the old Tails version are active 1.618
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.243
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.262
After features/support/hooks.rb:330 1.269
After features/support/hooks.rb:100 0.009
7:28.960
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 12.993
And no SquashFS delta is installed 0.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.078
And Tor is ready 19.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.677
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.361
Given I shutdown Tails and wait for the computer to power off 1:14.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.702
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.281
When the network is plugged 0.087
And Tor is ready 16.568
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.786
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.131
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.637
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.083
And Tor is ready 18.972
Then the Upgrader considers the system as up-to-date 0.302
# 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.029
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.580
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.036
34.981
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.030
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 17.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.490
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.000