Project Number Date
test_Tails_ISO_stable 6329 28 Apr 2026, 14:02

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:58.606 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:6.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.568
When I start Tails from USB drive "old" with network unplugged 47.185
Then the boot device has safe access rights 3.175
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:331 1.574
After features/support/hooks.rb:100 0.017
Tags: @product
1:28.233
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 57.023
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 25.203
And I take note of which tps features are available 0.738
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 4.329
After features/support/hooks.rb:331 0.679
After features/support/hooks.rb:100 0.007
Tags: @product
1:35.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.143
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.435
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.625
And all persistent directories from the old Tails version have safe access rights 2.441
And I take note of which tps features are available 0.176
And I shutdown Tails and wait for the computer to power off 8.154
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.179
After features/support/hooks.rb:331 0.300
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.477
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.247
And I log in to a new session 13.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.792
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.545
Then the running Tails is installed on USB drive "to_upgrade" 17.930
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 2.494
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.524
Then all tps features from the old Tails version are active 1.329
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 3.251
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.307
After features/support/hooks.rb:331 0.608
After features/support/hooks.rb:100 0.019
4:45.730
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.753
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.018
And Tor is ready 21.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.480
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.999
Given I shutdown Tails and wait for the computer to power off 20.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.025
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.191
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.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.220
When the network is plugged 0.016
And Tor is ready 21.464
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.400
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.993
Given I shutdown Tails and wait for the computer to power off 17.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.477
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.013
And Tor is ready 21.090
Then the Upgrader considers the system as up-to-date 0.106
# 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.151
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.466
After features/support/hooks.rb:331 0.729
After features/support/hooks.rb:100 0.012
26.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.892
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
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.019
And Tor is ready 17.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.406
After features/support/hooks.rb:331 0.734
After features/support/hooks.rb:100 0.000