Project Number Date
test_Tails_ISO_devel 4539 10 Aug 2026, 12:50

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:51.518 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.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.560
When I start Tails from USB drive "old" with network unplugged 49.310
Then the boot device has safe access rights 2.444
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.458
After features/support/hooks.rb:108 0.010
Tags: @product
1:27.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 52.275
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 24.142
And I take note of which tps features are available 7.471
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 2.790
After features/support/hooks.rb:339 0.219
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.001
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.390
Then Tails is running from USB drive "old" 0.275
And all tps features are active 8.493
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.912
And I take note of which tps features are available 6.578
And I shutdown Tails and wait for the computer to power off 2.706
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.679
After features/support/hooks.rb:339 0.344
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.699
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.530
And I log in to a new session 13.026
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.408
Then the running Tails is installed on USB drive "to_upgrade" 19.566
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.804
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.151
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.128
Then all tps features from the old Tails version are active 1.052
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.499
And the expected persistent files created with the old Tails version are present in the filesystem 1.070
And all persistent directories from the old Tails version have safe access rights 2.041
After features/support/hooks.rb:339 0.820
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:47.098
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.001
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
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.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.032
And Tor is ready 13.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.335
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.248
Given I shutdown Tails and wait for the computer to power off 5.525
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.935
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.826
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.184
When the network is plugged 0.027
And Tor is ready 11.095
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.437
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.251
Given I shutdown Tails and wait for the computer to power off 4.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.316
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.024
And Tor is ready 10.815
Then the Upgrader considers the system as up-to-date 0.092
# 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.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.418
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
20.817
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.368
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.319
And Tor is ready 10.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.001
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.000