Project Number Date
test_Tails_ISO_stable 6142 11 Feb 2026, 20:05

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:58.576 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:20.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.620
When I start Tails from USB drive "old" with network unplugged 1:0.250
Then the boot device has safe access rights 3.348
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:331 3.444
After features/support/hooks.rb:100 0.010
Tags: @product
1:37.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 59.627
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 28.308
And I take note of which tps features are available 1.109
Then a Tails persistence partition exists on USB drive "old" 0.705
And I shutdown Tails and wait for the computer to power off 7.214
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.007
Tags: @product
1:37.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.300
Then Tails is running from USB drive "old" 0.336
And all tps features are active 1.389
When I write some files expected to persist 1.680
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.321
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.717
And I take note of which tps features are available 0.259
And I shutdown Tails and wait for the computer to power off 8.649
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.943
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.015
Tags: @product
2:18.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.330
And I log in to a new session 12.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.086
And I plug USB drive "to_upgrade" 2.274
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.982
Then the running Tails is installed on USB drive "to_upgrade" 19.120
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.942
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.386
Then all tps features from the old Tails version are active 1.793
And Tails is running from USB drive "to_upgrade" 0.440
And the boot device has safe access rights 3.512
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:331 0.723
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:22.858
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.823
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.015
And Tor is ready 13.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.049
Given I shutdown Tails and wait for the computer to power off 7.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.856
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.659
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.298
When the network is plugged 0.025
And Tor is ready 12.076
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.211
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.702
Given I shutdown Tails and wait for the computer to power off 7.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.092
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.630
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
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.215
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.022
And Tor is ready 41.422
Then the Upgrader considers the system as up-to-date 0.156
# 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.982
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:331 0.783
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.120
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 7.750
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.595
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.000