Project Number Date
test_Tails_ISO_devel 4201 31 Jan 2026, 09:04

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 13:39.151 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:42.014
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.579
When I start Tails from USB drive "old" with network unplugged 1:6.359
Then the boot device has safe access rights 3.031
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 1.489
After features/support/hooks.rb:100 0.009
Tags: @product
1:39.430
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:0.962
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 28.599
And I take note of which tps features are available 1.039
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 7.757
After features/support/hooks.rb:331 0.523
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.074
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.527
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.779
When I write some files expected to persist 1.404
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.183
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.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.323
After features/support/hooks.rb:331 0.320
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.059
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 12.844
And I log in to a new session 12.148
And I clone USB drive "old" to a new USB drive "to_upgrade" 16.002
And I plug USB drive "to_upgrade" 2.687
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.107
Then the running Tails is installed on USB drive "to_upgrade" 18.885
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:331 2.426
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.379
Then all tps features from the old Tails version are active 1.313
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:331 0.741
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:5.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.604
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
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.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.046
And Tor is ready 14.167
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.603
Given I shutdown Tails and wait for the computer to power off 7.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.275
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.978
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.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.211
When the network is plugged 0.054
And Tor is ready 11.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.900
Given I shutdown Tails and wait for the computer to power off 7.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.737
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.848
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.240
When the network is plugged 0.052
And Tor is ready 12.867
Then the Upgrader considers the system as up-to-date 0.110
# 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.643
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.472
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.714
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 with a persistent partition enabled and logged in 10.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.443
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 10.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.689
After features/support/hooks.rb:331 1.146
After features/support/hooks.rb:100 0.000