Project Number Date
test_Tails_ISO_stable 6083 22 Jan 2026, 08:12

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 11:41.939 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:20.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
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 1:2.304
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 4.102
After features/support/hooks.rb:100 0.009
Tags: @product
1:28.149
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 54.976
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.710
And I take note of which tps features are available 0.706
Then a Tails persistence partition exists on USB drive "old" 0.654
And I shutdown Tails and wait for the computer to power off 6.770
After features/support/hooks.rb:331 0.253
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.182
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.351
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.221
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.982
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.179
After features/support/hooks.rb:331 0.179
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.670
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.627
And I log in to a new session 11.029
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.134
Then the running Tails is installed on USB drive "to_upgrade" 16.384
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.371
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.849
And the expected persistent files created with the old Tails version are present in the filesystem 1.197
And all persistent directories from the old Tails version have safe access rights 2.321
After features/support/hooks.rb:331 0.641
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:44.455
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.440
And no SquashFS delta is installed 0.071
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.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.019
And Tor is ready 13.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.053
Given I shutdown Tails and wait for the computer to power off 9.860
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.045
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.190
When the network is plugged 0.022
And Tor is ready 10.530
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.017
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.493
Given I shutdown Tails and wait for the computer to power off 7.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.515
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.590
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.013
And Tor is ready 10.015
Then the Upgrader considers the system as up-to-date 10.618
# 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.291
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:331 0.980
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
19.551
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.936
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.203
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.000