Project Number Date
test_Tails_ISO_stable 6057 13 Jan 2026, 13:42

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:10.790 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:7.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.747
When I start Tails from USB drive "old" with network unplugged 48.156
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.609
After features/support/hooks.rb:100 0.023
Tags: @product
1:27.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.246
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 24.060
And I take note of which tps features are available 0.843
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 7.930
After features/support/hooks.rb:331 0.314
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.020
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.140
When I write some files expected to persist 1.606
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 1.986
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 8.006
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.819
After features/support/hooks.rb:331 0.185
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.753
And I log in to a new session 10.519
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.872
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.087
Then the running Tails is installed on USB drive "to_upgrade" 16.247
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.587
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.112
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.939
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.000
After features/support/hooks.rb:331 0.936
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:27.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.422
And no SquashFS delta is installed 0.086
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.017
And Tor is ready 14.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.467
Given I shutdown Tails and wait for the computer to power off 9.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.032
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.190
When the network is plugged 0.031
And Tor is ready 11.698
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.118
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.169
Given I shutdown Tails and wait for the computer to power off 7.911
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.146
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.015
And Tor is ready 11.082
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 4.195
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.480
After features/support/hooks.rb:331 0.907
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
18.149
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 with a persistent partition enabled and logged in 7.722
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.044
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.000