Project Number Date
test_Tails_ISO_stable 6582 16 Aug 2026, 11:33

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:29.995 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:12.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.639
When I start Tails from USB drive "old" with network unplugged 54.653
Then the boot device has safe access rights 2.373
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.588
After features/support/hooks.rb:108 0.045
Tags: @product
1:21.719
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login 47.283
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.954
And I take note of which tps features are available 6.940
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 2.615
After features/support/hooks.rb:339 0.113
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.283
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.910
Then Tails is running from USB drive "old" 0.190
And all tps features are active 7.428
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 1.867
And I take note of which tps features are available 6.338
And I shutdown Tails and wait for the computer to power off 3.933
# 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.662
After features/support/hooks.rb:339 0.522
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.729
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 8.504
And I log in to a new session 12.500
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.705
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.923
Then the running Tails is installed on USB drive "to_upgrade" 17.604
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.524
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.465
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.227
And the expected persistent files created with the old Tails version are present in the filesystem 0.914
And all persistent directories from the old Tails version have safe access rights 1.483
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
3:28.563
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 8.435
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.025
And Tor is ready 12.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.184
Given I shutdown Tails and wait for the computer to power off 5.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.558
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.032
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.187
When the network is plugged 0.029
And Tor is ready 10.495
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.272
Given I shutdown Tails and wait for the computer to power off 2.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.165
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.579
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.027
And Tor is ready 10.251
Then the Upgrader considers the system as up-to-date 0.092
# 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.281
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
32.675
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 21.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 10.278
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.952
After features/support/hooks.rb:339 0.527
After features/support/hooks.rb:108 0.000