Project Number Date
test_Tails_ISO_devel 4225 10 Feb 2026, 16: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:8.519 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.784
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 14.020
When I start Tails from USB drive "old" with network unplugged 47.417
Then the boot device has safe access rights 2.595
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 3.848
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.822
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.904
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.922
And I take note of which tps features are available 0.744
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 4.437
After features/support/hooks.rb:331 0.600
After features/support/hooks.rb:100 0.031
Tags: @product
1:28.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.862
Then Tails is running from USB drive "old" 0.229
And all tps features are active 1.357
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 8.087
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.438
After features/support/hooks.rb:331 0.419
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.435
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.241
And I log in to a new session 12.531
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.830
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.898
Then the running Tails is installed on USB drive "to_upgrade" 17.421
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:331 3.928
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.746
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.491
Then all tps features from the old Tails version are active 1.247
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.764
And the expected persistent files created with the old Tails version are present in the filesystem 1.061
And all persistent directories from the old Tails version have safe access rights 1.869
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
4:12.521
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 with a persistent partition enabled and logged in 8.770
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.015
And Tor is ready 14.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.143
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.736
Given I shutdown Tails and wait for the computer to power off 17.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.577
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.225
When the network is plugged 0.017
And Tor is ready 10.336
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.964
Given I shutdown Tails and wait for the computer to power off 8.149
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.832
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.146
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.373
When the network is plugged 0.019
And Tor is ready 10.101
Then the Upgrader considers the system as up-to-date 10.765
# 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.843
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
19.261
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.146
After features/support/hooks.rb:331 0.966
After features/support/hooks.rb:100 0.000