Project Number Date
test_Tails_ISO_devel 4276 13 Mar 2026, 00:20

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:52.517 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:8.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 14.221
When I start Tails from USB drive "old" with network unplugged 49.590
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.743
After features/support/hooks.rb:100 0.013
Tags: @product
1:30.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 54.856
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.329
And I take note of which tps features are available 0.746
Then a Tails persistence partition exists on USB drive "old" 0.641
And I shutdown Tails and wait for the computer to power off 8.118
After features/support/hooks.rb:331 0.369
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.325
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.257
When I write some files expected to persist 1.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.144
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.160
And I take note of which tps features are available 0.198
And I shutdown Tails and wait for the computer to power off 4.090
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.573
After features/support/hooks.rb:331 0.585
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.381
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.445
And I log in to a new session 13.380
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.138
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.906
Then the running Tails is installed on USB drive "to_upgrade" 18.853
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 5.659
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.649
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.965
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.089
And all persistent directories from the old Tails version have safe access rights 1.932
After features/support/hooks.rb:331 0.610
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:46.376
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 9.173
And no SquashFS delta is installed 0.207
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.020
And Tor is ready 22.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.480
Given I shutdown Tails and wait for the computer to power off 20.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.825
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# 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.189
When the network is plugged 0.017
And Tor is ready 22.330
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.468
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.940
Given I shutdown Tails and wait for the computer to power off 17.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.361
Then Tails is running version 6.3~testoverlayfs 0.044
And all tps features are active 1.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.018
And Tor is ready 20.529
Then the Upgrader considers the system as up-to-date 0.131
# 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.908
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.458
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
26.851
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 7.819
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 18.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
After features/support/hooks.rb:331 0.870
After features/support/hooks.rb:100 0.000