Project Number Date
test_Tails_ISO_stable 6337 30 Apr 2026, 07:42

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:10.502 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:3.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.052
When I start Tails from USB drive "old" with network unplugged 45.237
Then the boot device has safe access rights 2.750
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.824
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 55.484
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 24.787
And I take note of which tps features are available 0.741
Then a Tails persistence partition exists on USB drive "old" 0.587
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:331 0.206
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.838
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 1:3.561
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.133
When I write some files expected to persist 1.266
# 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.446
And all persistent directories from the old Tails version have safe access rights 2.003
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 8.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.501
After features/support/hooks.rb:331 0.533
After features/support/hooks.rb:100 0.027
Tags: @product
2:21.295
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.518
And I log in to a new session 17.901
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.948
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.686
Then the running Tails is installed on USB drive "to_upgrade" 16.686
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:331 3.689
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.487
Then all tps features from the old Tails version are active 0.983
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 2.132
After features/support/hooks.rb:331 0.549
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:59.757
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 21.608
And no SquashFS delta is installed 0.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.027
And Tor is ready 24.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.411
Given I shutdown Tails and wait for the computer to power off 20.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.527
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.198
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.213
When the network is plugged 0.015
And Tor is ready 21.128
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.224
Given I shutdown Tails and wait for the computer to power off 17.432
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.362
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.022
And Tor is ready 21.339
Then the Upgrader considers the system as up-to-date 0.102
# 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.196
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.926
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
30.874
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.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 21.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.451
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.000