Project Number Date
test_Tails_ISO_stable 6538 28 Jul 2026, 12:55

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:22.580 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:0.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.245
When I start Tails from USB drive "old" with network unplugged 42.389
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 3.428
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.781
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 23.765
And I take note of which tps features are available 3.820
Then a Tails persistence partition exists on USB drive "old" 0.611
And I shutdown Tails and wait for the computer to power off 4.160
After features/support/hooks.rb:339 0.420
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.466
Then Tails is running from USB drive "old" 0.253
And all tps features are active 4.955
When I write some files expected to persist 1.185
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.822
And I take note of which tps features are available 3.523
And I shutdown Tails and wait for the computer to power off 3.991
# 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.968
After features/support/hooks.rb:339 0.139
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.654
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 without a persistent partition and stopped at Tails Greeter's login screen 7.490
And I log in to a new session 12.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.094
Then the running Tails is installed on USB drive "to_upgrade" 14.626
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.257
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.634
Then all tps features from the old Tails version are active 1.011
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.390
And the expected persistent files created with the old Tails version are present in the filesystem 0.984
And all persistent directories from the old Tails version have safe access rights 1.799
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
3:45.022
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 7.764
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.360
When the network is plugged 0.019
And Tor is ready 13.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.493
Given I shutdown Tails and wait for the computer to power off 6.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.418
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.815
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.248
When the network is plugged 0.015
And Tor is ready 10.617
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.670
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.781
Given I shutdown Tails and wait for the computer to power off 4.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.439
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.724
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.016
And Tor is ready 10.934
Then the Upgrader considers the system as up-to-date 10.531
# 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.179
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.791
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
21.493
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 7.325
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 11.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.567
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.000