Project Number Date
test_Tails_ISO_stable 6577 13 Aug 2026, 13:40

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:34.398 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
59.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.289
When I start Tails from USB drive "old" with network unplugged 41.375
Then the boot device has safe access rights 2.387
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 1.132
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 49.125
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.407
And I take note of which tps features are available 6.670
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 2.791
After features/support/hooks.rb:339 0.430
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.658
Then Tails is running from USB drive "old" 0.294
And all tps features are active 8.380
When I write some files expected to persist 1.065
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.128
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.617
And I take note of which tps features are available 6.621
And I shutdown Tails and wait for the computer to power off 4.055
# 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" 11.778
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.438
And I log in to a new session 13.520
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.613
Then the running Tails is installed on USB drive "to_upgrade" 18.992
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.870
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.069
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.277
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.154
And the boot device has safe access rights 2.420
And the expected persistent files created with the old Tails version are present in the filesystem 1.169
And all persistent directories from the old Tails version have safe access rights 1.854
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
3:46.451
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 with a persistent partition enabled and logged in 8.780
And no SquashFS delta is installed 0.086
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.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.050
And Tor is ready 12.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.122
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.599
Given I shutdown Tails and wait for the computer to power off 5.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.904
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 8.016
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.071
# 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.167
When the network is plugged 0.085
And Tor is ready 10.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.015
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.850
Given I shutdown Tails and wait for the computer to power off 3.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.260
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.407
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.026
And Tor is ready 10.544
Then the Upgrader considers the system as up-to-date 10.510
# 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.730
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.509
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 with a persistent partition enabled and logged in 7.962
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.517
After features/support/hooks.rb:339 0.651
After features/support/hooks.rb:108 0.000