Project Number Date
test_Tails_ISO_devel 4186 23 Jan 2026, 11:42

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:47.141 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.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.123
When I start Tails from USB drive "old" with network unplugged 50.644
Then the boot device has safe access rights 2.445
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.620
After features/support/hooks.rb:100 0.043
Tags: @product
1:26.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 53.681
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.691
And I take note of which tps features are available 0.744
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 6.763
After features/support/hooks.rb:331 0.631
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.685
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.261
When I write some files expected to persist 1.271
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.265
And all persistent directories from the old Tails version have safe access rights 1.836
And I take note of which tps features are available 0.156
And I shutdown Tails and wait for the computer to power off 4.234
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.115
After features/support/hooks.rb:331 0.443
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.301
And I log in to a new session 13.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.643
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.543
Then the running Tails is installed on USB drive "to_upgrade" 16.234
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.635
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.152
Then all tps features from the old Tails version are active 0.880
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 2.015
After features/support/hooks.rb:331 0.734
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:54.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.905
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.015
And Tor is ready 13.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.885
Given I shutdown Tails and wait for the computer to power off 17.669
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.520
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 1.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.180
When the network is plugged 0.018
And Tor is ready 9.768
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.129
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.093
Given I shutdown Tails and wait for the computer to power off 4.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.633
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.073
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.015
And Tor is ready 11.158
Then the Upgrader considers the system as up-to-date 10.629
# 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.373
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.729
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
20.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.071
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000