Project Number Date
test_Tails_ISO_devel 4351 19 Apr 2026, 11:18

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:47.360 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:3.966
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.074
When I start Tails from USB drive "old" with network unplugged 44.393
Then the boot device has safe access rights 3.549
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.682
After features/support/hooks.rb:100 0.020
Tags: @product
1:28.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 53.206
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 25.209
And I take note of which tps features are available 0.782
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 8.186
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.033
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.305
When I write some files expected to persist 1.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.155
And I take note of which tps features are available 0.292
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.441
After features/support/hooks.rb:331 0.516
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.134
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.210
And I log in to a new session 17.451
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.949
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.181
Then the running Tails is installed on USB drive "to_upgrade" 16.789
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.430
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.265
Then all tps features from the old Tails version are active 1.179
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.988
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.192
After features/support/hooks.rb:331 0.630
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:44.113
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 8.465
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.015
And Tor is ready 23.348
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.114
Given I shutdown Tails and wait for the computer to power off 21.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.232
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 1.476
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.243
When the network is plugged 0.018
And Tor is ready 20.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.485
Given I shutdown Tails and wait for the computer to power off 17.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.938
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.395
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.032
And Tor is ready 21.996
Then the Upgrader considers the system as up-to-date 0.108
# 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.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.429
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
26.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.450
After features/support/hooks.rb:331 1.013
After features/support/hooks.rb:100 0.000