Project Number Date
test_Tails_ISO_devel 4305 30 Mar 2026, 15:13

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:24.159 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:9.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.338
When I start Tails from USB drive "old" with network unplugged 51.380
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 1.285
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.398
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 53.324
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 23.658
And I take note of which tps features are available 0.628
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 7.909
After features/support/hooks.rb:331 0.460
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.108
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.236
When I write some files expected to persist 1.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 1.966
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.014
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.357
After features/support/hooks.rb:331 0.344
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.501
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 without a persistent partition and stopped at Tails Greeter's login screen 8.472
And I log in to a new session 11.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.772
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.914
Then the running Tails is installed on USB drive "to_upgrade" 14.867
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:331 1.853
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.087
Then all tps features from the old Tails version are active 0.968
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 2.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.096
And all persistent directories from the old Tails version have safe access rights 2.030
After features/support/hooks.rb:331 0.714
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
4:35.281
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.275
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.015
And Tor is ready 20.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.714
Given I shutdown Tails and wait for the computer to power off 19.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.604
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.151
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.197
When the network is plugged 0.020
And Tor is ready 20.729
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.998
Given I shutdown Tails and wait for the computer to power off 17.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.965
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.079
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.017
And Tor is ready 22.463
Then the Upgrader considers the system as up-to-date 0.144
# 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.962
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
27.470
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 7.570
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.000