Project Number Date
test_Tails_ISO_devel 4179 20 Jan 2026, 08:52

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 11:14.591 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:12.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
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.850
When I start Tails from USB drive "old" with network unplugged 53.635
Then the boot device has safe access rights 2.833
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:331 3.809
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.153
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 23.972
And I take note of which tps features are available 0.838
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:331 0.472
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.380
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 "old" with network unplugged and I login with persistence enabled 1:0.950
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.245
When I write some files expected to persist 1.322
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 2.338
And I take note of which tps features are available 0.367
And I shutdown Tails and wait for the computer to power off 8.138
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.287
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.367
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.553
And I log in to a new session 11.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.849
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.702
Then the running Tails is installed on USB drive "to_upgrade" 16.401
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 3.725
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.264
Then all tps features from the old Tails version are active 1.007
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.653
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 2.146
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.048
Tags: @product @automatic_upgrade
3:23.514
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 8.020
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.167
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 0.029
And Tor is ready 13.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.928
Given I shutdown Tails and wait for the computer to power off 9.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.515
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.088
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.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.017
And Tor is ready 11.231
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.246
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.375
Given I shutdown Tails and wait for the computer to power off 2.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.196
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.287
When the network is plugged 0.016
And Tor is ready 10.466
Then the Upgrader considers the system as up-to-date 0.107
# 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 3.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
18.948
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.743
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.877
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.007
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.000