Project Number Date
test_Tails_ISO_stable 6516 21 Jul 2026, 17:27

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:36.146 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:13.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.061
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.835
When I start Tails from USB drive "old" with network unplugged 53.776
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:339 3.874
After features/support/hooks.rb:108 0.014
Tags: @product
1:34.770
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 56.712
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 25.636
And I take note of which tps features are available 4.644
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 6.885
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.005
Tags: @product
1:42.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.547
Then Tails is running from USB drive "old" 0.228
And all tps features are active 5.548
When I write some files expected to persist 1.617
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.149
And I take note of which tps features are available 4.421
And I shutdown Tails and wait for the computer to power off 4.388
# 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" 12.950
After features/support/hooks.rb:339 0.392
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.192
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.658
And I log in to a new session 13.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.801
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.284
Then the running Tails is installed on USB drive "to_upgrade" 16.369
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.402
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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:11.860
Then all tps features from the old Tails version are active 1.115
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 3.128
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.318
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:10.636
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 with a persistent partition enabled and logged in 8.729
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
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.339
When the network is plugged 0.013
And Tor is ready 14.013
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.329
Given I shutdown Tails and wait for the computer to power off 7.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.230
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.175
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.237
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.3~testoverlayfs 3.196
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.519
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.482
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.714
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.013
And Tor is ready 11.751
Then the Upgrader considers the system as up-to-date 10.535
# 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.396
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.910
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.749
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 8.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.877
After features/support/hooks.rb:339 1.211
After features/support/hooks.rb:108 0.000