Project Number Date
test_Tails_ISO_devel 4596 04 Sep 2026, 11:11

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 10:58.278 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:11.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.228
When I start Tails from USB drive "old" with network unplugged 54.255
Then the boot device has safe access rights 1.901
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.160
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.501
After features/support/hooks.rb:108 0.019
Tags: @product
1:17.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 44.869
Then Tails is running from USB drive "old" 0.186
And I create a persistent partition 23.204
And I take note of which tps features are available 6.160
Then a Tails persistence partition exists on USB drive "old" 0.473
And I shutdown Tails and wait for the computer to power off 2.614
After features/support/hooks.rb:339 0.263
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.248
Then Tails is running from USB drive "old" 0.207
And all tps features are active 6.637
When I write some files expected to persist 0.988
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.218
And all persistent directories from the old Tails version have safe access rights 1.587
And I take note of which tps features are available 6.125
And I shutdown Tails and wait for the computer to power off 2.510
# 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" 10.763
After features/support/hooks.rb:339 0.306
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.450
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.006
And I log in to a new session 9.865
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.564
And I plug USB drive "to_upgrade" 2.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.243
Then the running Tails is installed on USB drive "to_upgrade" 17.315
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.580
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.123
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.962
Then all tps features from the old Tails version are active 0.964
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 1.873
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.455
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.006
3:31.584
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.860
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.275
When the network is plugged 0.032
And Tor is ready 13.151
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.604
Given I shutdown Tails and wait for the computer to power off 5.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.935
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.159
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.086
# 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.140
When the network is plugged 0.038
And Tor is ready 10.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.852
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.444
Given I shutdown Tails and wait for the computer to power off 2.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.508
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.027
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.031
And Tor is ready 10.107
Then the Upgrader considers the system as up-to-date 10.420
# 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.451
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.238
After features/support/hooks.rb:339 0.729
After features/support/hooks.rb:108 0.009
19.613
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 with a persistent partition enabled and logged in 7.992
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.447
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.000