Project Number Date
test_Tails_ISO_stable 6322 22 Apr 2026, 11:45

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 13:12.170 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:9.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.412
When I start Tails from USB drive "old" with network unplugged 49.941
Then the boot device has safe access rights 2.972
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.239
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 1.447
After features/support/hooks.rb:100 0.010
Tags: @product
1:26.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 56.115
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 24.295
And I take note of which tps features are available 0.809
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 4.215
After features/support/hooks.rb:331 0.375
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.279
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.143
When I write some files expected to persist 1.403
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.548
And all persistent directories from the old Tails version have safe access rights 2.452
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 4.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.302
After features/support/hooks.rb:331 0.534
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.041
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.291
And I log in to a new session 17.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.872
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.870
Then the running Tails is installed on USB drive "to_upgrade" 17.131
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 3.648
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.940
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.082
And the expected persistent files created with the old Tails version are present in the filesystem 1.241
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:331 0.572
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
4:58.776
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 9.461
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.019
And Tor is ready 27.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.711
Given I shutdown Tails and wait for the computer to power off 19.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.276
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.213
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.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.215
When the network is plugged 0.020
And Tor is ready 22.418
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.448
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.193
Given I shutdown Tails and wait for the computer to power off 17.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.107
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.019
And Tor is ready 22.223
Then the Upgrader considers the system as up-to-date 0.170
# 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 5.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.512
After features/support/hooks.rb:331 0.943
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
29.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.001
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.936
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.597
After features/support/hooks.rb:331 0.729
After features/support/hooks.rb:100 0.000