Project Number Date
test_Tails_ISO_devel 4149 04 Jan 2026, 11:29

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 10:41.358 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
56.744
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.059
When I start Tails from USB drive "old" with network unplugged 39.603
Then the boot device has safe access rights 2.352
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.871
After features/support/hooks.rb:100 0.018
Tags: @product
1:22.430
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 49.105
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.761
And I take note of which tps features are available 0.827
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 7.914
After features/support/hooks.rb:331 0.433
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.163
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.100
When I write some files expected to persist 1.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
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.698
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 7.773
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.668
After features/support/hooks.rb:331 0.310
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.134
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 without a persistent partition and stopped at Tails Greeter's login screen 8.189
And I log in to a new session 12.245
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.126
Then the running Tails is installed on USB drive "to_upgrade" 14.369
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.562
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.714
Then all tps features from the old Tails version are active 1.038
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.540
And the expected persistent files created with the old Tails version are present in the filesystem 1.099
And all persistent directories from the old Tails version have safe access rights 1.755
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
3:27.136
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.043
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.016
And Tor is ready 12.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.924
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.350
Given I shutdown Tails and wait for the computer to power off 5.692
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.640
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.197
When the network is plugged 0.014
And Tor is ready 10.743
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.280
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.368
Given I shutdown Tails and wait for the computer to power off 7.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.090
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.022
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.118
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 9.781
Then the Upgrader considers the system as up-to-date 10.517
# 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 3.726
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:331 0.770
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
18.998
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.557
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.481
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.640
After features/support/hooks.rb:331 0.800
After features/support/hooks.rb:100 0.000