Project Number Date
test_Tails_ISO_devel 4177 19 Jan 2026, 15:30

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 10:57.517 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
58.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
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" 13.659
When I start Tails from USB drive "old" with network unplugged 39.997
Then the boot device has safe access rights 2.571
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 3.563
After features/support/hooks.rb:100 0.032
Tags: @product
1:25.158
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.523
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 23.098
And I take note of which tps features are available 0.792
Then a Tails persistence partition exists on USB drive "old" 0.490
And I shutdown Tails and wait for the computer to power off 7.973
After features/support/hooks.rb:331 0.182
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.758
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.021
When I write some files expected to persist 1.452
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
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.060
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 7.943
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.913
After features/support/hooks.rb:331 0.284
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.641
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 8.249
And I log in to a new session 9.977
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.499
Then the running Tails is installed on USB drive "to_upgrade" 15.643
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 6.863
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.253
Then all tps features from the old Tails version are active 1.225
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 2.074
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
3:34.387
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.371
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.374
When the network is plugged 0.018
And Tor is ready 12.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.068
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.631
Given I shutdown Tails and wait for the computer to power off 9.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.370
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.197
When the network is plugged 0.017
And Tor is ready 10.704
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.093
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.390
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.343
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.100
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.050
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.016
And Tor is ready 11.058
Then the Upgrader considers the system as up-to-date 10.556
# 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.340
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.453
After features/support/hooks.rb:331 1.004
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
19.554
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 7.574
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 8.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.470
After features/support/hooks.rb:331 0.678
After features/support/hooks.rb:100 0.000