Project Number Date
test_Tails_ISO_devel 4345 15 Apr 2026, 08:02

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:9.489 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:4.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.518
When I start Tails from USB drive "old" with network unplugged 45.022
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 1.154
After features/support/hooks.rb:100 0.009
Tags: @product
1:28.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 56.206
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 25.839
And I take note of which tps features are available 0.774
Then a Tails persistence partition exists on USB drive "old" 0.710
And I shutdown Tails and wait for the computer to power off 4.627
After features/support/hooks.rb:331 0.372
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.295
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.126
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.265
When I write some files expected to persist 1.325
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.659
And all persistent directories from the old Tails version have safe access rights 2.181
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 8.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.587
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.028
Tags: @product
2:19.333
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 without a persistent partition and stopped at Tails Greeter's login screen 8.100
And I log in to a new session 17.587
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.276
Then the running Tails is installed on USB drive "to_upgrade" 18.037
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:331 3.490
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.210
Then all tps features from the old Tails version are active 0.989
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 3.145
And the expected persistent files created with the old Tails version are present in the filesystem 1.304
And all persistent directories from the old Tails version have safe access rights 2.411
After features/support/hooks.rb:331 0.883
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
4:54.750
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 9.022
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.014
And Tor is ready 24.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.569
Given I shutdown Tails and wait for the computer to power off 16.746
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.587
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.387
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.205
When the network is plugged 0.032
And Tor is ready 20.450
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.166
Given I shutdown Tails and wait for the computer to power off 18.144
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.462
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.015
And Tor is ready 22.484
Then the Upgrader considers the system as up-to-date 0.160
# 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.801
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.785
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
31.718
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 22.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
After features/support/hooks.rb:331 1.059
After features/support/hooks.rb:100 0.000