Project Number Date
test_Tails_ISO_stable 6245 29 Mar 2026, 10:56

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:3.438 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:16.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.018
When I start Tails from USB drive "old" with network unplugged 58.862
Then the boot device has safe access rights 2.659
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:331 1.612
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.783
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.683
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.236
And I take note of which tps features are available 0.685
Then a Tails persistence partition exists on USB drive "old" 0.602
And I shutdown Tails and wait for the computer to power off 8.263
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.455
Then Tails is running from USB drive "old" 0.296
And all tps features are active 1.051
When I write some files expected to persist 1.238
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 1.688
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 4.174
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.929
After features/support/hooks.rb:331 0.183
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.004
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.411
And I log in to a new session 12.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.665
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.286
Then the running Tails is installed on USB drive "to_upgrade" 14.598
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.549
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.795
Then all tps features from the old Tails version are active 0.890
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.381
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.915
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.006
4:18.307
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 7.909
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.016
And Tor is ready 19.886
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.690
Given I shutdown Tails and wait for the computer to power off 19.764
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.580
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.178
When the network is plugged 0.018
And Tor is ready 20.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.645
Given I shutdown Tails and wait for the computer to power off 18.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.385
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.015
And Tor is ready 21.507
Then the Upgrader considers the system as up-to-date 0.117
# 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.211
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.660
After features/support/hooks.rb:100 0.010
24.000
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 7.412
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 15.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.343
After features/support/hooks.rb:331 0.698
After features/support/hooks.rb:100 0.000