Project Number Date
test_Tails_ISO_devel 4174 17 Jan 2026, 12:22

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:18.514 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:23.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.776
When I start Tails from USB drive "old" with network unplugged 47.405
Then the boot device has safe access rights 3.047
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 3.910
After features/support/hooks.rb:100 0.008
Tags: @product
1:39.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:0.870
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 28.447
And I take note of which tps features are available 1.087
Then a Tails persistence partition exists on USB drive "old" 0.712
And I shutdown Tails and wait for the computer to power off 7.539
After features/support/hooks.rb:331 0.340
After features/support/hooks.rb:100 0.009
Tags: @product
1:43.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.528
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.776
When I write some files expected to persist 1.453
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.169
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 7.562
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.508
After features/support/hooks.rb:331 0.412
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.638
And I log in to a new session 13.249
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.514
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.937
Then the running Tails is installed on USB drive "to_upgrade" 19.254
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 3.776
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.155
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.547
Then all tps features from the old Tails version are active 1.351
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.059
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.188
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:21.453
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 26.508
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.059
And Tor is ready 13.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.641
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.994
Given I shutdown Tails and wait for the computer to power off 10.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.154
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.011
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.188
When the network is plugged 0.048
And Tor is ready 12.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.819
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.127
Given I shutdown Tails and wait for the computer to power off 3.202
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.834
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.054
And Tor is ready 12.227
Then the Upgrader considers the system as up-to-date 0.114
# 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.276
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.553
After features/support/hooks.rb:331 1.182
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
21.595
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.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 10.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.656
After features/support/hooks.rb:331 0.798
After features/support/hooks.rb:100 0.000