Project Number Date
test_Tails_ISO_devel 4175 18 Jan 2026, 12:10

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 12:59.006 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
1:19.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 26.365
When I start Tails from USB drive "old" with network unplugged 47.872
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:331 3.825
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:0.331
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 28.734
And I take note of which tps features are available 1.097
Then a Tails persistence partition exists on USB drive "old" 0.645
And I shutdown Tails and wait for the computer to power off 3.107
After features/support/hooks.rb:331 0.576
After features/support/hooks.rb:100 0.008
Tags: @product
1:44.774
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.831
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.724
When I write some files expected to persist 1.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.148
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 7.594
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.626
After features/support/hooks.rb:331 0.636
After features/support/hooks.rb:100 0.015
Tags: @product
2:19.932
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 without a persistent partition and stopped at Tails Greeter's login screen 9.894
And I log in to a new session 9.434
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.555
And I plug USB drive "to_upgrade" 2.300
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.471
Then the running Tails is installed on USB drive "to_upgrade" 18.881
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 3.978
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.147
Then all tps features from the old Tails version are active 1.431
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.973
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.353
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
3:51.034
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 9.309
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.056
And Tor is ready 12.537
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.738
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.470
Given I shutdown Tails and wait for the computer to power off 3.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.220
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.245
When the network is plugged 0.081
And Tor is ready 11.852
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.640
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.467
Given I shutdown Tails and wait for the computer to power off 7.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.933
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.971
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.051
And Tor is ready 11.639
Then the Upgrader considers the system as up-to-date 0.141
# 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 5.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.521
After features/support/hooks.rb:331 1.096
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
49.640
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 9.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 39.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.636
After features/support/hooks.rb:331 0.779
After features/support/hooks.rb:100 0.000