Project Number Date
test_Tails_ISO_stable 6568 10 Aug 2026, 11:42

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:58.712 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:16.158
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.266
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 14.244
When I start Tails from USB drive "old" with network unplugged 57.878
Then the boot device has safe access rights 2.129
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.377
After features/support/hooks.rb:108 0.028
Tags: @product
1:25.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 50.112
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 24.743
And I take note of which tps features are available 7.165
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 2.681
After features/support/hooks.rb:339 0.152
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.333
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.492
Then Tails is running from USB drive "old" 0.263
And all tps features are active 8.153
When I write some files expected to persist 1.364
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 1.864
And I take note of which tps features are available 6.236
And I shutdown Tails and wait for the computer to power off 4.208
# 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.856
After features/support/hooks.rb:339 0.543
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.217
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.908
And I log in to a new session 13.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.292
Then the running Tails is installed on USB drive "to_upgrade" 19.518
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 6.695
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.560
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.740
Then all tps features from the old Tails version are active 1.468
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.758
And the expected persistent files created with the old Tails version are present in the filesystem 1.174
And all persistent directories from the old Tails version have safe access rights 2.059
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:39.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.668
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.024
And Tor is ready 12.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.123
Given I shutdown Tails and wait for the computer to power off 5.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.609
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.933
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.199
When the network is plugged 0.050
And Tor is ready 11.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.998
Given I shutdown Tails and wait for the computer to power off 3.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.996
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.027
And Tor is ready 10.649
Then the Upgrader considers the system as up-to-date 0.100
# 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.683
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 1.021
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
27.942
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.006
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.027
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 18.429
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.219
After features/support/hooks.rb:339 0.766
After features/support/hooks.rb:108 0.000