Project Number Date
test_Tails_ISO_stable 6250 31 Mar 2026, 11: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:35.691 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:37.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.152
When I start Tails from USB drive "old" with network unplugged 1:18.189
Then the boot device has safe access rights 3.188
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.612
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 1:0.618
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 24.114
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 8.407
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.008
Tags: @product
1:24.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.191
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.133
When I write some files expected to persist 1.490
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.144
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 4.251
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.463
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.445
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.935
And I log in to a new session 22.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.842
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.616
Then the running Tails is installed on USB drive "to_upgrade" 16.705
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:331 4.087
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
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.917
Then all tps features from the old Tails version are active 0.919
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.471
And the expected persistent files created with the old Tails version are present in the filesystem 1.200
And all persistent directories from the old Tails version have safe access rights 1.935
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:43.363
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 with a persistent partition enabled and logged in 9.242
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.027
And Tor is ready 27.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.886
Given I shutdown Tails and wait for the computer to power off 17.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.454
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.188
When the network is plugged 0.014
And Tor is ready 20.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.143
Given I shutdown Tails and wait for the computer to power off 17.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.226
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.013
And Tor is ready 22.198
Then the Upgrader considers the system as up-to-date 0.104
# 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.151
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.524
After features/support/hooks.rb:331 0.675
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
28.109
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 7.798
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
After features/support/hooks.rb:331 0.636
After features/support/hooks.rb:100 0.000