Project Number Date
test_Tails_ISO_stable 6641 06 Sep 2026, 11:37

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 11:1.556 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
55.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.581
When I start Tails from USB drive "old" with network unplugged 37.880
Then the boot device has safe access rights 2.131
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.687
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.998
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 47.991
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 23.689
And I take note of which tps features are available 6.415
Then a Tails persistence partition exists on USB drive "old" 0.471
And I shutdown Tails and wait for the computer to power off 5.107
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.280
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.886
Then Tails is running from USB drive "old" 0.221
And all tps features are active 7.186
When I write some files expected to persist 1.298
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 1.371
And I take note of which tps features are available 6.231
And I shutdown Tails and wait for the computer to power off 2.779
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.860
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.335
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.327
And I log in to a new session 10.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.628
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.807
Then the running Tails is installed on USB drive "to_upgrade" 18.252
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:339 1.965
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.347
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 1.893
And the expected persistent files created with the old Tails version are present in the filesystem 0.955
And all persistent directories from the old Tails version have safe access rights 1.550
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.006
3:28.861
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.201
And no SquashFS delta is installed 0.080
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.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.035
And Tor is ready 10.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.195
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.449
Given I shutdown Tails and wait for the computer to power off 5.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.016
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.601
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.206
When the network is plugged 0.030
And Tor is ready 10.504
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.865
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.546
Given I shutdown Tails and wait for the computer to power off 2.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.849
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.027
And Tor is ready 10.190
Then the Upgrader considers the system as up-to-date 0.118
# 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.507
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 1.008
After features/support/hooks.rb:108 0.012
20.627
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.305
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 10.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.542
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.000