Project Number Date
test_Tails_ISO_devel 4307 31 Mar 2026, 11:29

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 13:5.618 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:4.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.093
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.824
When I start Tails from USB drive "old" with network unplugged 45.508
Then the boot device has safe access rights 2.895
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.142
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 54.109
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 25.059
And I take note of which tps features are available 0.773
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 4.318
After features/support/hooks.rb:331 0.159
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.453
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.845
Then Tails is running from USB drive "old" 0.210
And all tps features are active 1.486
When I write some files expected to persist 1.511
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.564
And all persistent directories from the old Tails version have safe access rights 2.268
And I take note of which tps features are available 0.195
And I shutdown Tails and wait for the computer to power off 8.176
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.916
After features/support/hooks.rb:331 0.444
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.395
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.073
And I log in to a new session 16.930
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.738
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.234
Then the running Tails is installed on USB drive "to_upgrade" 16.770
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:331 3.106
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.618
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.361
Then all tps features from the old Tails version are active 0.951
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.640
And the expected persistent files created with the old Tails version are present in the filesystem 1.194
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:331 0.772
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:6.331
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.425
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.015
And Tor is ready 23.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.797
Given I shutdown Tails and wait for the computer to power off 19.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.717
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.057
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.202
When the network is plugged 0.013
And Tor is ready 21.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.749
Given I shutdown Tails and wait for the computer to power off 17.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.894
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.453
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.013
And Tor is ready 40.319
Then the Upgrader considers the system as up-to-date 0.127
# 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.763
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
28.582
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.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 20.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
After features/support/hooks.rb:331 0.950
After features/support/hooks.rb:100 0.000