Project Number Date
test_Tails_ISO_devel 4356 21 Apr 2026, 18:13

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:45.626 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:2.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.921
When I start Tails from USB drive "old" with network unplugged 43.484
Then the boot device has safe access rights 3.110
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 3.879
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login 56.184
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 24.967
And I take note of which tps features are available 0.846
Then a Tails persistence partition exists on USB drive "old" 0.669
And I shutdown Tails and wait for the computer to power off 8.307
After features/support/hooks.rb:331 0.552
After features/support/hooks.rb:100 0.006
Tags: @product
1:34.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.735
Then Tails is running from USB drive "old" 0.271
And all tps features are active 1.159
When I write some files expected to persist 1.461
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 2.130
And I take note of which tps features are available 0.190
And I shutdown Tails and wait for the computer to power off 8.232
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.222
After features/support/hooks.rb:331 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.752
And I log in to a new session 13.021
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.940
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.475
Then the running Tails is installed on USB drive "to_upgrade" 16.212
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:331 2.075
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.814
Then all tps features from the old Tails version are active 1.010
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 3.724
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.140
After features/support/hooks.rb:331 0.706
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:39.394
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.596
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.016
And Tor is ready 22.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.617
Given I shutdown Tails and wait for the computer to power off 6.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.884
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.217
When the network is plugged 0.015
And Tor is ready 21.509
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.243
Given I shutdown Tails and wait for the computer to power off 18.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.919
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.359
When the network is plugged 0.019
And Tor is ready 21.614
Then the Upgrader considers the system as up-to-date 0.110
# 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.047
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.480
After features/support/hooks.rb:331 1.075
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
26.738
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 7.742
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 18.151
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.427
After features/support/hooks.rb:331 1.119
After features/support/hooks.rb:100 0.000