Project Number Date
test_Tails_ISO_devel 4210 04 Feb 2026, 14:25

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 11:19.080 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:1.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.263
When I start Tails from USB drive "old" with network unplugged 42.870
Then the boot device has safe access rights 2.717
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.471
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 53.503
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 25.287
And I take note of which tps features are available 0.761
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 7.947
After features/support/hooks.rb:331 0.546
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.906
Then Tails is running from USB drive "old" 0.228
And all tps features are active 1.139
When I write some files expected to persist 1.293
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.076
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 4.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.905
After features/support/hooks.rb:331 0.388
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.378
And I log in to a new session 10.471
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.752
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.248
Then the running Tails is installed on USB drive "to_upgrade" 15.592
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:331 3.842
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.000
Then all tps features from the old Tails version are active 0.962
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 1.919
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
3:43.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.624
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.016
And Tor is ready 12.704
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.528
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.121
Given I shutdown Tails and wait for the computer to power off 9.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.125
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.249
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.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.224
When the network is plugged 0.015
And Tor is ready 9.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.246
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.846
Given I shutdown Tails and wait for the computer to power off 8.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.596
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.014
And Tor is ready 11.997
Then the Upgrader considers the system as up-to-date 10.508
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.479
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
20.852
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 with a persistent partition enabled and logged in 7.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.148
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.000