Project Number Date
test_Tails_ISO_stable 6111 31 Jan 2026, 11:48

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:51.809 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:44.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.197
When I start Tails from USB drive "old" with network unplugged 1:25.156
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 1.852
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 54.536
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 24.368
And I take note of which tps features are available 0.782
Then a Tails persistence partition exists on USB drive "old" 0.707
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:331 0.321
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.975
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 "old" with network unplugged and I login with persistence enabled 1:1.667
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.234
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.053
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 4.313
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.219
After features/support/hooks.rb:331 0.402
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.261
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 without a persistent partition and stopped at Tails Greeter's login screen 9.002
And I log in to a new session 13.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.907
And I plug USB drive "to_upgrade" 2.272
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.881
Then the running Tails is installed on USB drive "to_upgrade" 19.582
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:331 0.637
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.249
Then all tps features from the old Tails version are active 0.966
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.512
And the expected persistent files created with the old Tails version are present in the filesystem 1.183
And all persistent directories from the old Tails version have safe access rights 1.965
After features/support/hooks.rb:331 0.526
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:18.374
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 9.177
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.018
And Tor is ready 43.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.622
Given I shutdown Tails and wait for the computer to power off 11.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.587
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.117
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.131
# 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.188
When the network is plugged 0.015
And Tor is ready 11.842
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.009
Given I shutdown Tails and wait for the computer to power off 8.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.322
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.365
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.015
And Tor is ready 12.173
Then the Upgrader considers the system as up-to-date 10.492
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:331 0.721
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
20.785
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.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
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.069
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.784
After features/support/hooks.rb:331 1.262
After features/support/hooks.rb:100 0.000