Project Number Date
test_Tails_ISO_devel 4641 28 Sep 2026, 17:31

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:9.459 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
56.653
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.712
When I start Tails from USB drive "old" with network unplugged 39.095
Then the boot device has safe access rights 2.146
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.441
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 47.648
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.202
And I take note of which tps features are available 6.896
Then a Tails persistence partition exists on USB drive "old" 0.644
And I shutdown Tails and wait for the computer to power off 2.620
After features/support/hooks.rb:339 0.501
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.273
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.906
Then Tails is running from USB drive "old" 0.199
And all tps features are active 7.198
When I write some files expected to persist 1.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.700
And I take note of which tps features are available 6.107
And I shutdown Tails and wait for the computer to power off 2.557
# 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.702
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.014
Tags: @product
2:12.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.296
And I log in to a new session 11.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.663
And I plug USB drive "to_upgrade" 2.296
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.051
Then the running Tails is installed on USB drive "to_upgrade" 18.270
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 1.818
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.641
Then all tps features from the old Tails version are active 1.227
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.127
And all persistent directories from the old Tails version have safe access rights 1.746
After features/support/hooks.rb:339 0.719
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:39.827
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.315
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.031
And Tor is ready 12.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.477
Given I shutdown Tails and wait for the computer to power off 5.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.610
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.481
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.032
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.075
# 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.187
When the network is plugged 0.025
And Tor is ready 10.247
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.799
Given I shutdown Tails and wait for the computer to power off 2.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.473
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.418
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.211
When the network is plugged 0.051
And Tor is ready 10.101
Then the Upgrader considers the system as up-to-date 10.492
# 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.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 1.033
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.514
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.189
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.309
After features/support/hooks.rb:339 0.657
After features/support/hooks.rb:108 0.000