Project Number Date
test_Tails_ISO_devel 4516 28 Jul 2026, 11:28

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:17.928 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:4.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.262
When I start Tails from USB drive "old" with network unplugged 45.737
Then the boot device has safe access rights 2.728
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.627
After features/support/hooks.rb:108 0.060
Tags: @product
1:36.313
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 59.172
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 27.287
And I take note of which tps features are available 4.809
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 4.114
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.173
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.402
Then Tails is running from USB drive "old" 0.324
And all tps features are active 5.758
When I write some files expected to persist 1.607
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 1.881
And I take note of which tps features are available 4.090
And I shutdown Tails and wait for the computer to power off 4.185
# 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" 12.361
After features/support/hooks.rb:339 0.194
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.622
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 without a persistent partition and stopped at Tails Greeter's login screen 7.947
And I log in to a new session 14.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.836
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.311
Then the running Tails is installed on USB drive "to_upgrade" 16.496
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:339 1.121
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.289
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.388
Then all tps features from the old Tails version are active 1.189
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.798
And the expected persistent files created with the old Tails version are present in the filesystem 1.290
And all persistent directories from the old Tails version have safe access rights 2.263
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:0.511
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.051
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
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.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.673
When the network is plugged 0.015
And Tor is ready 13.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.630
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.344
Given I shutdown Tails and wait for the computer to power off 7.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.392
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.639
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.220
When the network is plugged 0.015
And Tor is ready 10.124
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.530
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.922
Given I shutdown Tails and wait for the computer to power off 4.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.997
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.873
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.042
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.015
And Tor is ready 9.829
Then the Upgrader considers the system as up-to-date 10.615
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
21.512
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.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.141
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.015
And Tor is ready 10.521
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.057
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.000