Project Number Date
test_Tails_ISO_stable 6559 04 Aug 2026, 14:26

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:34.937 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
59.651
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.692
When I start Tails from USB drive "old" with network unplugged 41.949
Then the boot device has safe access rights 2.128
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 3.436
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.230
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 48.926
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 23.645
And I take note of which tps features are available 6.723
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 4.118
After features/support/hooks.rb:339 0.143
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.848
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.430
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.810
When I write some files expected to persist 1.075
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.194
And all persistent directories from the old Tails version have safe access rights 1.505
And I take note of which tps features are available 6.497
And I shutdown Tails and wait for the computer to power off 2.648
# 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.223
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.560
And I log in to a new session 12.528
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.802
And I plug USB drive "to_upgrade" 2.307
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.711
Then the running Tails is installed on USB drive "to_upgrade" 17.955
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.631
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.098
Then all tps features from the old Tails version are active 1.084
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.158
And all persistent directories from the old Tails version have safe access rights 1.783
After features/support/hooks.rb:339 0.677
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:58.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.730
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.160
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.031
And Tor is ready 11.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.652
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 5.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.877
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.505
And the file system changes introduced in version 6.2~testoverlayfs are present 0.183
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.164
When the network is plugged 0.022
And Tor is ready 10.144
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.980
Given I shutdown Tails and wait for the computer to power off 3.917
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.567
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.880
And the file system changes introduced in version 6.3~testoverlayfs are present 0.298
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.027
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 10.443
# 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.756
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.391
After features/support/hooks.rb:339 0.974
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.702
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.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.106
After features/support/hooks.rb:339 1.000
After features/support/hooks.rb:108 0.000