Project Number Date
test_Tails_ISO_stable 6696 28 Sep 2026, 12:14

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 15:11.057 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.806
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.979
When I start Tails from USB drive "old" with network unplugged 42.739
Then the boot device has safe access rights 2.348
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.714
After features/support/hooks.rb:108 0.021
Tags: @product
1:23.976
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 49.016
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 23.408
And I take note of which tps features are available 6.666
Then a Tails persistence partition exists on USB drive "old" 0.449
And I shutdown Tails and wait for the computer to power off 4.081
After features/support/hooks.rb:339 0.346
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.796
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 "old" with network unplugged and I login with persistence enabled 1:3.267
Then Tails is running from USB drive "old" 0.265
And all tps features are active 7.407
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.257
And all persistent directories from the old Tails version have safe access rights 1.638
And I take note of which tps features are available 6.186
And I shutdown Tails and wait for the computer to power off 2.582
# 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.542
After features/support/hooks.rb:339 0.543
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.099
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.172
And I log in to a new session 11.998
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.694
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.501
Then the running Tails is installed on USB drive "to_upgrade" 18.249
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 1.665
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.324
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.311
Then all tps features from the old Tails version are active 1.176
And Tails is running from USB drive "to_upgrade" 0.172
And the boot device has safe access rights 2.152
And the expected persistent files created with the old Tails version are present in the filesystem 0.909
And all persistent directories from the old Tails version have safe access rights 1.513
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
7:30.560
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.056
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.175
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.322
When the network is plugged 0.025
And Tor is ready 13.132
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.588
Given I shutdown Tails and wait for the computer to power off 5.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.010
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.247
When the network is plugged 0.029
And Tor is ready 10.579
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4:2.802
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.540
Given I shutdown Tails and wait for the computer to power off 2.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.281
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 8.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.029
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.035
And Tor is ready 11.249
Then the Upgrader considers the system as up-to-date 0.076
# 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.143
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.532
After features/support/hooks.rb:339 1.011
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.494
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.681
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.286
After features/support/hooks.rb:339 0.677
After features/support/hooks.rb:108 0.000