Project Number Date
test_Tails_ISO_stable 6013 18 Dec 2025, 13:10

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:21.692 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.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 30.649
When I start Tails from USB drive "old" with network unplugged 1:5.853
Then the boot device has safe access rights 3.043
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 3.824
After features/support/hooks.rb:100 0.009
Tags: @product
1:33.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:1.290
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 26.856
And I take note of which tps features are available 1.127
Then a Tails persistence partition exists on USB drive "old" 0.720
And I shutdown Tails and wait for the computer to power off 3.004
After features/support/hooks.rb:331 0.429
After features/support/hooks.rb:100 0.009
Tags: @product
1:44.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.665
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.765
When I write some files expected to persist 1.389
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 1.990
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 7.431
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.696
After features/support/hooks.rb:331 0.547
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.651
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.097
And I log in to a new session 15.805
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.163
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.094
Then the running Tails is installed on USB drive "to_upgrade" 19.729
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:331 3.795
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.222
Then all tps features from the old Tails version are active 1.289
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 2.093
After features/support/hooks.rb:331 0.780
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:6.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.731
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.051
And Tor is ready 13.529
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.662
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.435
Given I shutdown Tails and wait for the computer to power off 7.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.348
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.897
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.180
# 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.219
When the network is plugged 0.068
And Tor is ready 12.694
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.565
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.093
Given I shutdown Tails and wait for the computer to power off 7.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.591
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.875
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.057
And Tor is ready 10.112
Then the Upgrader considers the system as up-to-date 10.602
# 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.133
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:331 1.182
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.650
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.666
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.629
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.000