Project Number Date
test_Tails_ISO_stable 6264 05 Apr 2026, 07:10

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:47.131 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:20.834
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.173
When I start Tails from USB drive "old" with network unplugged 1:2.261
Then the boot device has safe access rights 2.597
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.749
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.960
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 56.969
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 24.832
And I take note of which tps features are available 0.907
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.514
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.077
When I write some files expected to persist 1.375
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.010
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.031
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.067
After features/support/hooks.rb:331 0.253
After features/support/hooks.rb:100 0.006
Tags: @product
2:14.277
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.885
And I log in to a new session 13.305
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.084
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.323
Then the running Tails is installed on USB drive "to_upgrade" 17.142
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 4.059
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.440
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 2.821
And the expected persistent files created with the old Tails version are present in the filesystem 1.184
And all persistent directories from the old Tails version have safe access rights 2.067
After features/support/hooks.rb:331 0.848
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:34.836
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.341
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.013
And Tor is ready 21.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.450
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.685
Given I shutdown Tails and wait for the computer to power off 18.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.185
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.295
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.221
When the network is plugged 0.018
And Tor is ready 21.246
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.743
Given I shutdown Tails and wait for the computer to power off 13.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.442
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.018
And Tor is ready 20.892
Then the Upgrader considers the system as up-to-date 0.101
# 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.017
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:331 0.798
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
26.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.731
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.041
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 17.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
After features/support/hooks.rb:331 0.791
After features/support/hooks.rb:100 0.000