Project Number Date
test_Tails_ISO_devel 4448 15 Jun 2026, 15:25

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:26.585 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:5.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 14.168
When I start Tails from USB drive "old" with network unplugged 46.840
Then the boot device has safe access rights 2.866
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 3.790
After features/support/hooks.rb:108 0.019
Tags: @product
1:34.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 55.605
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 25.978
And I take note of which tps features are available 4.740
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 7.146
After features/support/hooks.rb:339 0.330
After features/support/hooks.rb:108 0.020
Tags: @product
1:45.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.424
Then Tails is running from USB drive "old" 0.267
And all tps features are active 5.577
When I write some files expected to persist 1.435
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 2.406
And I take note of which tps features are available 4.761
And I shutdown Tails and wait for the computer to power off 7.320
# 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.996
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.017
Tags: @product
2:14.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.893
And I log in to a new session 13.828
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.993
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.697
Then the running Tails is installed on USB drive "to_upgrade" 16.041
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 2.044
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.769
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.050
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.911
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 2.196
After features/support/hooks.rb:339 0.864
After features/support/hooks.rb:108 0.023
4:3.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.365
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.016
And Tor is ready 14.486
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.277
Given I shutdown Tails and wait for the computer to power off 10.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.529
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.888
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.209
# 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.245
When the network is plugged 0.018
And Tor is ready 10.076
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.766
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.288
Given I shutdown Tails and wait for the computer to power off 3.058
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.302
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 6.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.016
And Tor is ready 10.361
Then the Upgrader considers the system as up-to-date 10.660
# 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 5.036
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.045
21.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.834
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.364
After features/support/hooks.rb:339 1.017
After features/support/hooks.rb:108 0.000