Project Number Date
test_Tails_ISO_devel 4369 30 Apr 2026, 16:09

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 13:22.209 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:21.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.095
When I start Tails from USB drive "old" with network unplugged 1:1.714
Then the boot device has safe access rights 3.153
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.160
After features/support/hooks.rb:331 3.810
After features/support/hooks.rb:100 0.020
Tags: @product
1:32.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 57.982
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 26.135
And I take note of which tps features are available 0.881
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 6.938
After features/support/hooks.rb:331 0.340
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.331
Then Tails is running from USB drive "old" 0.377
And all tps features are active 1.656
When I write some files expected to persist 1.373
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 7.022
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.644
After features/support/hooks.rb:331 0.431
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.310
And I log in to a new session 17.976
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.831
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.519
Then the running Tails is installed on USB drive "to_upgrade" 16.207
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 3.705
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.378
Then all tps features from the old Tails version are active 1.058
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 3.096
And the expected persistent files created with the old Tails version are present in the filesystem 1.294
And all persistent directories from the old Tails version have safe access rights 2.169
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
4:50.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.014
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.354
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.017
And Tor is ready 22.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.457
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.072
Given I shutdown Tails and wait for the computer to power off 19.744
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.717
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.392
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.215
When the network is plugged 0.015
And Tor is ready 21.874
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.481
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 17.598
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.977
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.021
And Tor is ready 20.962
Then the Upgrader considers the system as up-to-date 0.106
# 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.325
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 1.097
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
29.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.241
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 20.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 1.217
After features/support/hooks.rb:100 0.000