Project Number Date
test_Tails_ISO_devel 4525 31 Jul 2026, 11:17

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:23.629 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:8.380
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.058
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.057
When I start Tails from USB drive "old" with network unplugged 51.486
Then the boot device has safe access rights 2.075
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.736
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.092
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.859
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 23.459
And I take note of which tps features are available 3.853
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 4.077
After features/support/hooks.rb:339 0.230
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.652
Then Tails is running from USB drive "old" 0.232
And all tps features are active 4.663
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.768
And I take note of which tps features are available 3.611
And I shutdown Tails and wait for the computer to power off 2.666
# 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.706
After features/support/hooks.rb:339 0.304
After features/support/hooks.rb:108 0.007
Tags: @product
2:7.791
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.818
And I log in to a new session 11.501
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.270
Then the running Tails is installed on USB drive "to_upgrade" 13.957
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.204
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.041
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.581
Then all tps features from the old Tails version are active 0.874
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.720
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.051
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.980
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.015
And Tor is ready 13.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.824
Given I shutdown Tails and wait for the computer to power off 6.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.125
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.773
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.236
When the network is plugged 0.048
And Tor is ready 10.504
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.290
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.880
Given I shutdown Tails and wait for the computer to power off 4.052
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.852
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.012
And Tor is ready 10.063
Then the Upgrader considers the system as up-to-date 10.575
# 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.740
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.419
After features/support/hooks.rb:339 0.851
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.275
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.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.721
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.000