Project Number Date
test_Tails_ISO_devel 4614 14 Sep 2026, 11:14

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:4.944 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
57.203
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.449
When I start Tails from USB drive "old" with network unplugged 39.700
Then the boot device has safe access rights 2.291
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.578
After features/support/hooks.rb:108 0.010
Tags: @product
1:22.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login 48.993
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 24.010
And I take note of which tps features are available 6.521
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 2.548
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.993
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.664
Then Tails is running from USB drive "old" 0.209
And all tps features are active 6.817
When I write some files expected to persist 1.220
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.132
And all persistence configuration files have safe access rights 0.230
And all persistent directories from the old Tails version have safe access rights 1.632
And I take note of which tps features are available 6.961
And I shutdown Tails and wait for the computer to power off 5.180
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.831
After features/support/hooks.rb:339 0.306
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.675
And I log in to a new session 11.996
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.708
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.212
Then the running Tails is installed on USB drive "to_upgrade" 18.463
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.686
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.136
Then all tps features from the old Tails version are active 1.263
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.345
And the expected persistent files created with the old Tails version are present in the filesystem 1.120
And all persistent directories from the old Tails version have safe access rights 1.797
After features/support/hooks.rb:339 0.712
After features/support/hooks.rb:108 0.006
3:28.334
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.102
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.278
When the network is plugged 0.029
And Tor is ready 12.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.044
Given I shutdown Tails and wait for the computer to power off 5.650
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.373
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.688
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.211
When the network is plugged 0.027
And Tor is ready 10.700
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.661
Given I shutdown Tails and wait for the computer to power off 2.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.291
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.023
And Tor is ready 10.255
Then the Upgrader considers the system as up-to-date 0.090
# 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.110
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 1.129
After features/support/hooks.rb:108 0.016
18.890
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.818
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.000