Project Number Date
test_Tails_ISO_21171-trixie-13.6 4 13 Jul 2026, 18:12

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:10.302 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:8.971
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.022
When I start Tails from USB drive "old" with network unplugged 49.810
Then the boot device has safe access rights 3.001
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.492
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 3.599
After features/support/hooks.rb:108 0.008
Tags: @product
1:35.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 55.726
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 25.401
And I take note of which tps features are available 4.733
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 8.265
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.008
Tags: @product
1:36.764
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.151
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.831
Then Tails is running from USB drive "old" 0.258
And all tps features are active 5.154
When I write some files expected to persist 1.207
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 2.006
And I take note of which tps features are available 4.191
And I shutdown Tails and wait for the computer to power off 4.194
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.325
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.627
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.966
And I log in to a new session 12.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.740
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.808
Then the running Tails is installed on USB drive "to_upgrade" 17.162
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:339 2.241
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.307
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.031
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.632
And the expected persistent files created with the old Tails version are present in the filesystem 1.223
And all persistent directories from the old Tails version have safe access rights 2.065
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.064
Tags: @product @automatic_upgrade
3:59.301
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.275
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.015
And Tor is ready 12.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.816
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.720
Given I shutdown Tails and wait for the computer to power off 9.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.578
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 6.027
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.231
When the network is plugged 0.015
And Tor is ready 10.264
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.684
Given I shutdown Tails and wait for the computer to power off 4.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.173
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.270
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.038
And Tor is ready 9.994
Then the Upgrader considers the system as up-to-date 10.592
# 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 4.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.652
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
21.030
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.239
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.710
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.000