Project Number Date
test_Tails_ISO_stable 6665 14 Sep 2026, 20:49

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:32.892 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:3.245
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.841
When I start Tails from USB drive "old" with network unplugged 45.194
Then the boot device has safe access rights 2.471
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.339
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.292
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 49.480
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 23.943
And I take note of which tps features are available 6.148
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 3.916
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.577
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.412
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.746
And I take note of which tps features are available 6.646
And I shutdown Tails and wait for the computer to power off 2.659
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.672
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.767
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.823
And I log in to a new session 11.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.984
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.775
Then the running Tails is installed on USB drive "to_upgrade" 19.037
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.614
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.314
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.139
Then all tps features from the old Tails version are active 1.229
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.515
And the expected persistent files created with the old Tails version are present in the filesystem 1.129
And all persistent directories from the old Tails version have safe access rights 1.962
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
3:45.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.611
And no SquashFS delta is installed 0.065
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.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.283
When the network is plugged 0.025
And Tor is ready 12.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.204
Given I shutdown Tails and wait for the computer to power off 5.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.302
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 8.632
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.155
When the network is plugged 0.031
And Tor is ready 10.644
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.964
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.211
Given I shutdown Tails and wait for the computer to power off 4.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.250
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.414
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.027
And Tor is ready 10.302
Then the Upgrader considers the system as up-to-date 10.501
# 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 3.707
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.543
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 9.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.495
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.000