Project Number Date
test_Tails_ISO_devel 4478 01 Jul 2026, 11:16

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:37.031 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:7.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.313
When I start Tails from USB drive "old" with network unplugged 49.859
Then the boot device has safe access rights 2.487
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.679
After features/support/hooks.rb:108 0.017
Tags: @product
1:29.905
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 52.761
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 24.314
And I take note of which tps features are available 3.997
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 8.000
After features/support/hooks.rb:339 0.442
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.548
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.042
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.034
Then Tails is running from USB drive "old" 0.243
And all tps features are active 4.830
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.309
And all persistent directories from the old Tails version have safe access rights 1.995
And I take note of which tps features are available 3.959
And I shutdown Tails and wait for the computer to power off 7.863
# 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.821
After features/support/hooks.rb:339 0.304
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.174
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.044
And I log in to a new session 11.701
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.678
Then the running Tails is installed on USB drive "to_upgrade" 14.426
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.091
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.805
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.006
3:47.885
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 7.996
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.015
And Tor is ready 13.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.350
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.435
Given I shutdown Tails and wait for the computer to power off 6.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.002
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.571
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.211
When the network is plugged 0.014
And Tor is ready 11.444
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.788
Given I shutdown Tails and wait for the computer to power off 8.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.189
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.860
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.015
And Tor is ready 11.121
Then the Upgrader considers the system as up-to-date 10.490
# 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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.367
After features/support/hooks.rb:339 0.993
After features/support/hooks.rb:108 0.012
19.400
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 7.276
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.043
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.383
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.387
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.000