Project Number Date
test_Tails_ISO_devel 3897 05 Jul 2025, 14: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 25:53.553 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
3:0.365
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.131
Given a computer 0.793
And I create a 7200 MiB disk named "old" 0.155
And I plug USB drive "old" 1.399
And I write an old version of the Tails USB image to disk "old" 40.269
When I start Tails from USB drive "old" with network unplugged 2:8.752
Then the boot device has safe access rights 4.775
And Tails is running from USB drive "old" 2.139
And there is no persistence partition on USB drive "old" 0.616
And process "udev-watchdog" is running 0.181
And udev-watchdog is monitoring the correct device 0.902
And I unplug USB drive "old" 0.379
After features/support/hooks.rb:330 5.807
After features/support/hooks.rb:100 0.013
Tags: @product
2:46.427
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login 1:49.221
Then Tails is running from USB drive "old" 3.059
And I create a persistent partition 42.956
And I take note of which tps features are available 2.883
Then a Tails persistence partition exists on USB drive "old" 1.074
And I shutdown Tails and wait for the computer to power off 6.967
After features/support/hooks.rb:330 0.348
After features/support/hooks.rb:100 0.049
Tags: @product
4:10.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:14.020
Then Tails is running from USB drive "old" 0.549
And all tps features are active 2.109
When I write some files expected to persist 1.890
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.376
And all persistence configuration files have safe access rights 0.531
And all persistent directories from the old Tails version have safe access rights 6.802
And I take note of which tps features are available 1.184
And I shutdown Tails and wait for the computer to power off 7.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.830
After features/support/hooks.rb:330 0.361
After features/support/hooks.rb:100 0.027
Tags: @product
3:20.363
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.026
And I log in to a new session 29.324
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.571
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.307
Then the running Tails is installed on USB drive "to_upgrade" 38.952
And I unplug USB drive "to_upgrade" 1.233
And I unplug USB drive "__internal" 0.425
After features/support/hooks.rb:330 4.259
After features/support/hooks.rb:100 0.000
Tags: @product
3:1.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:44.364
Then all tps features from the old Tails version are active 2.330
And Tails is running from USB drive "to_upgrade" 2.402
And the boot device has safe access rights 7.831
And the expected persistent files created with the old Tails version are present in the filesystem 1.841
And all persistent directories from the old Tails version have safe access rights 2.532
After features/support/hooks.rb:330 2.017
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
8:46.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.069
And no SquashFS delta is installed 0.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.608
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.389
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.658
When the network is plugged 0.072
And Tor is ready 32.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.951
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.634
Given I shutdown Tails and wait for the computer to power off 14.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.948
Then Tails is running version 6.2~testoverlayfs 0.470
And all tps features are active 5.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.410
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.405
When the network is plugged 0.099
And Tor is ready 22.270
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.182
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.610
Given I shutdown Tails and wait for the computer to power off 4.567
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.210
Then Tails is running version 6.3~testoverlayfs 0.203
And all tps features are active 5.343
And the file system changes introduced in version 6.3~testoverlayfs are present 0.864
And only the 6.3~testoverlayfs SquashFS delta is installed 0.144
# 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.542
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.600
When the network is plugged 0.102
And Tor is ready 24.231
Then the Upgrader considers the system as up-to-date 0.366
# 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 22.614
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 5.152
After features/support/hooks.rb:330 3.661
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
47.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.380
And the signing key used by the Upgrader is outdated 0.671
But a current signing key is available on our website 0.000
When the network is plugged 0.404
And Tor is ready 25.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.264
After features/support/hooks.rb:330 1.477
After features/support/hooks.rb:100 0.000