Project Number Date
test_Tails_ISO_devel 4311 01 Apr 2026, 18:34

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:45.754 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:11.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.738
When I start Tails from USB drive "old" with network unplugged 52.886
Then the boot device has safe access rights 2.706
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.210
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.291
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 57.222
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 25.882
And I take note of which tps features are available 0.852
Then a Tails persistence partition exists on USB drive "old" 0.611
And I shutdown Tails and wait for the computer to power off 8.364
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.658
Then Tails is running from USB drive "old" 0.266
And all tps features are active 1.309
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.726
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.521
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.389
After features/support/hooks.rb:331 0.255
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.658
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.900
And I log in to a new session 14.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.078
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.502
Then the running Tails is installed on USB drive "to_upgrade" 17.384
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 1.937
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.407
Then all tps features from the old Tails version are active 0.955
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 2.153
After features/support/hooks.rb:331 0.673
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:16.684
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 9.529
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.015
And Tor is ready 23.127
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.748
Given I shutdown Tails and wait for the computer to power off 21.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.684
Then Tails is running version 6.2~testoverlayfs 0.042
And all tps features are active 1.666
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.200
# 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.230
When the network is plugged 0.018
And Tor is ready 22.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.947
Given I shutdown Tails and wait for the computer to power off 18.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.590
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.387
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.042
And Tor is ready 40.190
Then the Upgrader considers the system as up-to-date 0.108
# 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.787
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.585
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
40.116
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 20.619
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
After features/support/hooks.rb:331 0.686
After features/support/hooks.rb:100 0.000