Project Number Date
test_Tails_ISO_devel 4197 28 Jan 2026, 22:27

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:48.932 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:4.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.227
When I start Tails from USB drive "old" with network unplugged 46.637
Then the boot device has safe access rights 2.800
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 3.549
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.050
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 53.692
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 23.501
And I take note of which tps features are available 0.724
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.839
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.287
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 1.893
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 4.291
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.653
After features/support/hooks.rb:331 0.490
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.281
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 without a persistent partition and stopped at Tails Greeter's login screen 8.577
And I log in to a new session 11.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.946
And I plug USB drive "to_upgrade" 2.325
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.738
Then the running Tails is installed on USB drive "to_upgrade" 15.266
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:331 2.090
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.477
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.021
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.735
And the expected persistent files created with the old Tails version are present in the filesystem 1.159
And all persistent directories from the old Tails version have safe access rights 2.153
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:9.850
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 7.894
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.021
And Tor is ready 12.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.926
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.697
Given I shutdown Tails and wait for the computer to power off 9.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.429
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.221
When the network is plugged 0.015
And Tor is ready 40.928
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.485
Given I shutdown Tails and wait for the computer to power off 8.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.383
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.018
And Tor is ready 11.765
Then the Upgrader considers the system as up-to-date 10.561
# 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.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.625
After features/support/hooks.rb:331 0.660
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
21.371
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 7.989
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.953
After features/support/hooks.rb:331 0.869
After features/support/hooks.rb:100 0.000