Project Number Date
test_Tails_ISO_devel 4195 27 Jan 2026, 20:21

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:22.562 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:2.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.985
When I start Tails from USB drive "old" with network unplugged 44.251
Then the boot device has safe access rights 2.784
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.950
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.256
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.774
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.114
And I take note of which tps features are available 0.650
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 6.816
After features/support/hooks.rb:331 0.613
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.351
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.070
When I write some files expected to persist 1.176
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 2.045
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 8.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.935
After features/support/hooks.rb:331 0.516
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.642
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.506
And I log in to a new session 10.614
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.148
Then the running Tails is installed on USB drive "to_upgrade" 16.069
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:331 1.761
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.967
Then all tps features from the old Tails version are active 0.929
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.576
And the expected persistent files created with the old Tails version are present in the filesystem 1.397
And all persistent directories from the old Tails version have safe access rights 2.375
After features/support/hooks.rb:331 0.653
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
3:42.303
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 8.850
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.016
And Tor is ready 13.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.954
Given I shutdown Tails and wait for the computer to power off 10.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.671
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.128
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.196
When the network is plugged 0.044
And Tor is ready 11.357
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.250
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.754
Given I shutdown Tails and wait for the computer to power off 8.013
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.815
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.187
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.014
And Tor is ready 11.870
Then the Upgrader considers the system as up-to-date 10.596
# 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.426
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:331 0.608
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
21.157
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 8.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.572
After features/support/hooks.rb:331 0.575
After features/support/hooks.rb:100 0.000