Project Number Date
test_Tails_ISO_stable 6213 17 Mar 2026, 20:26

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:28.175 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:32.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
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" 14.574
When I start Tails from USB drive "old" with network unplugged 1:13.119
Then the boot device has safe access rights 3.174
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.859
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 57.574
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 25.204
And I take note of which tps features are available 0.865
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 8.198
After features/support/hooks.rb:331 0.509
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.183
Then Tails is running from USB drive "old" 0.324
And all tps features are active 1.340
When I write some files expected to persist 1.395
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.508
And all persistent directories from the old Tails version have safe access rights 2.152
And I take note of which tps features are available 0.214
And I shutdown Tails and wait for the computer to power off 8.011
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.264
After features/support/hooks.rb:331 0.210
After features/support/hooks.rb:100 0.006
Tags: @product
2:24.785
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.618
And I log in to a new session 14.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.330
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.745
Then the running Tails is installed on USB drive "to_upgrade" 17.775
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:331 3.290
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.921
Then all tps features from the old Tails version are active 1.005
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.832
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 2.005
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:39.049
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.406
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.022
And Tor is ready 24.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.737
Given I shutdown Tails and wait for the computer to power off 9.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.074
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.301
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.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.239
When the network is plugged 0.016
And Tor is ready 21.926
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.505
Given I shutdown Tails and wait for the computer to power off 17.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.849
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.199
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.016
And Tor is ready 20.782
Then the Upgrader considers the system as up-to-date 0.168
# 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.340
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 0.977
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
30.734
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.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 21.461
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
After features/support/hooks.rb:331 1.069
After features/support/hooks.rb:100 0.000