Project Number Date
test_Tails_ISO_stable 6068 15 Jan 2026, 12:25

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 14:31.486 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:41.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 31.439
When I start Tails from USB drive "old" with network unplugged 1:4.597
Then the boot device has safe access rights 3.598
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:331 4.243
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:1.990
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 29.600
And I take note of which tps features are available 1.184
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 7.665
After features/support/hooks.rb:331 0.329
After features/support/hooks.rb:100 0.009
Tags: @product
1:48.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.543
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.904
When I write some files expected to persist 1.496
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.168
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 7.974
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.053
After features/support/hooks.rb:331 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.622
And I log in to a new session 14.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.687
And I plug USB drive "to_upgrade" 2.575
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.042
Then the running Tails is installed on USB drive "to_upgrade" 22.307
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 3.990
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.788
Then all tps features from the old Tails version are active 1.594
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.360
And the expected persistent files created with the old Tails version are present in the filesystem 1.363
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.009
4:49.402
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 12.844
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.065
And Tor is ready 15.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.859
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.091
Given I shutdown Tails and wait for the computer to power off 11.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.749
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.180
# 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.238
When the network is plugged 0.051
And Tor is ready 12.609
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.930
Given I shutdown Tails and wait for the computer to power off 7.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.972
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.054
And Tor is ready 41.541
Then the Upgrader considers the system as up-to-date 0.105
# 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.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.463
After features/support/hooks.rb:331 0.849
After features/support/hooks.rb:100 0.015
22.998
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 10.381
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 11.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.580
After features/support/hooks.rb:331 1.183
After features/support/hooks.rb:100 0.000