Project Number Date
test_Tails_ISO_stable 6018 21 Dec 2025, 11:47

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:13.716 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:41.622
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.483
When I start Tails from USB drive "old" with network unplugged 1:6.144
Then the boot device has safe access rights 2.899
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 3.772
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:0.446
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 26.768
And I take note of which tps features are available 1.188
Then a Tails persistence partition exists on USB drive "old" 0.663
And I shutdown Tails and wait for the computer to power off 7.412
After features/support/hooks.rb:331 0.431
After features/support/hooks.rb:100 0.009
Tags: @product
1:39.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.651
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.725
When I write some files expected to persist 1.547
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.114
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 7.418
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.559
After features/support/hooks.rb:331 0.425
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.368
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 12.208
And I log in to a new session 16.618
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.701
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.910
Then the running Tails is installed on USB drive "to_upgrade" 20.025
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 4.152
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.449
Then all tps features from the old Tails version are active 1.327
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.084
And the expected persistent files created with the old Tails version are present in the filesystem 1.230
And all persistent directories from the old Tails version have safe access rights 2.133
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:0.616
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 with a persistent partition enabled and logged in 11.650
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.090
And Tor is ready 14.508
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.667
Given I shutdown Tails and wait for the computer to power off 12.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.391
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.893
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.228
When the network is plugged 0.050
And Tor is ready 12.461
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.669
Given I shutdown Tails and wait for the computer to power off 3.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.435
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.860
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.065
And Tor is ready 11.563
Then the Upgrader considers the system as up-to-date 0.110
# 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.370
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.938
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.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 11.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.613
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.000