Project Number Date
test_Tails_ISO_devel 4444 12 Jun 2026, 11:24

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:13.435 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:0.609
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.739
When I start Tails from USB drive "old" with network unplugged 42.148
Then the boot device has safe access rights 2.715
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 1.261
After features/support/hooks.rb:108 0.018
Tags: @product
1:32.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 55.829
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.562
And I take note of which tps features are available 4.291
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 7.014
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.017
Tags: @product
1:40.924
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.677
Then Tails is running from USB drive "old" 0.291
And all tps features are active 5.110
When I write some files expected to persist 1.407
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.226
And I take note of which tps features are available 4.384
And I shutdown Tails and wait for the computer to power off 7.061
# 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" 13.009
After features/support/hooks.rb:339 0.445
After features/support/hooks.rb:108 0.019
Tags: @product
2:12.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.386
And I log in to a new session 13.216
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.863
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.545
Then the running Tails is installed on USB drive "to_upgrade" 15.907
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 2.375
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.159
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.421
Then all tps features from the old Tails version are active 1.305
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.172
And all persistent directories from the old Tails version have safe access rights 2.127
After features/support/hooks.rb:339 0.686
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:8.085
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.052
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.017
And Tor is ready 12.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.239
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.888
Given I shutdown Tails and wait for the computer to power off 9.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.239
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# 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.235
When the network is plugged 0.013
And Tor is ready 11.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.885
Given I shutdown Tails and wait for the computer to power off 8.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.569
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 4.671
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.018
And Tor is ready 11.946
Then the Upgrader considers the system as up-to-date 10.570
# 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.414
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.047
Tags: @product @automatic_upgrade
21.577
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.965
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.191
After features/support/hooks.rb:339 0.648
After features/support/hooks.rb:108 0.000