Project Number Date
test_Tails_ISO_stable 6589 18 Aug 2026, 18:06

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:44.069 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:5.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.567
When I start Tails from USB drive "old" with network unplugged 47.614
Then the boot device has safe access rights 2.398
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.720
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 47.639
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 23.234
And I take note of which tps features are available 9.308
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 2.590
After features/support/hooks.rb:339 0.261
After features/support/hooks.rb:108 0.011
Tags: @product
1:41.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.434
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.802
Then Tails is running from USB drive "old" 0.283
And all tps features are active 9.226
When I write some files expected to persist 1.308
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 1.819
And I take note of which tps features are available 7.737
And I shutdown Tails and wait for the computer to power off 4.131
# 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.005
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.006
Tags: @product
2:28.333
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 21.554
And I log in to a new session 13.224
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.873
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.757
Then the running Tails is installed on USB drive "to_upgrade" 18.445
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 4.116
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.214
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.340
And the expected persistent files created with the old Tails version are present in the filesystem 0.967
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:339 0.865
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:34.381
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.910
And no SquashFS delta is installed 0.077
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.027
And Tor is ready 13.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.208
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.689
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.657
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.159
When the network is plugged 0.029
And Tor is ready 10.321
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.058
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.741
Given I shutdown Tails and wait for the computer to power off 3.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.765
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.938
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.031
And Tor is ready 10.167
Then the Upgrader considers the system as up-to-date 0.068
# 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.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.282
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
19.239
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.029
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.542
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.341
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.000