Project Number Date
test_Tails_ISO_stable 6205 16 Mar 2026, 06:50

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 12:9.706 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.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.043
When I start Tails from USB drive "old" with network unplugged 54.026
Then the boot device has safe access rights 2.612
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.719
After features/support/hooks.rb:100 0.080
Tags: @product
1:24.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 51.641
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.299
And I take note of which tps features are available 0.651
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 8.150
After features/support/hooks.rb:331 0.360
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.898
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.055
When I write some files expected to persist 1.309
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 1.693
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 7.908
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.898
After features/support/hooks.rb:331 0.423
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.461
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 without a persistent partition and stopped at Tails Greeter's login screen 8.286
And I log in to a new session 11.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.816
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.306
Then the running Tails is installed on USB drive "to_upgrade" 15.312
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:331 2.371
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.187
Then all tps features from the old Tails version are active 1.124
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.644
And the expected persistent files created with the old Tails version are present in the filesystem 1.136
And all persistent directories from the old Tails version have safe access rights 1.876
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:26.672
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 7.937
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
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.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.015
And Tor is ready 20.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.362
Given I shutdown Tails and wait for the computer to power off 19.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.667
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.010
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.185
When the network is plugged 0.016
And Tor is ready 20.479
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.843
Given I shutdown Tails and wait for the computer to power off 16.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.295
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.217
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.015
And Tor is ready 20.818
Then the Upgrader considers the system as up-to-date 0.091
# 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.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 0.622
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.474
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 7.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
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.063
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 16.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.747
After features/support/hooks.rb:100 0.000