Project Number Date
test_Tails_ISO_devel 4341 14 Apr 2026, 12:55

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.217 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:15.579
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.704
When I start Tails from USB drive "old" with network unplugged 57.237
Then the boot device has safe access rights 2.908
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 3.523
After features/support/hooks.rb:100 0.018
Tags: @product
1:32.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 57.143
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 25.212
And I take note of which tps features are available 0.971
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.372
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.017
Tags: @product
1:35.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.464
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.498
When I write some files expected to persist 1.520
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.702
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.575
After features/support/hooks.rb:331 0.548
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.220
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.697
And I log in to a new session 14.060
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.844
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.838
Then the running Tails is installed on USB drive "to_upgrade" 17.171
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:331 2.129
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.207
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.624
And the expected persistent files created with the old Tails version are present in the filesystem 1.990
And all persistent directories from the old Tails version have safe access rights 2.123
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
4:46.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.957
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.015
And Tor is ready 20.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.632
Given I shutdown Tails and wait for the computer to power off 19.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.877
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.347
When the network is plugged 0.028
And Tor is ready 21.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.449
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.821
Given I shutdown Tails and wait for the computer to power off 18.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.545
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 1.245
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.046
And Tor is ready 22.068
Then the Upgrader considers the system as up-to-date 0.140
# 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.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:331 0.791
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
25.609
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.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.491
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.368
After features/support/hooks.rb:331 0.649
After features/support/hooks.rb:100 0.000