Project Number Date
test_Tails_ISO_21250-forbid-modify-self-memory 1 17 Aug 2026, 12: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 11:58.022 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:7.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.706
When I start Tails from USB drive "old" with network unplugged 49.825
Then the boot device has safe access rights 2.317
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.440
After features/support/hooks.rb:108 0.051
Tags: @product
1:29.173
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 53.143
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 24.034
And I take note of which tps features are available 6.640
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 4.097
After features/support/hooks.rb:339 0.204
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.786
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.562
Then Tails is running from USB drive "old" 0.270
And all tps features are active 7.997
When I write some files expected to persist 1.156
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 1.718
And I take note of which tps features are available 7.137
And I shutdown Tails and wait for the computer to power off 2.581
# 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.645
After features/support/hooks.rb:339 0.557
After features/support/hooks.rb:108 0.006
Tags: @product
2:29.555
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 22.951
And I log in to a new session 12.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.837
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.326
Then the running Tails is installed on USB drive "to_upgrade" 19.394
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 3.606
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.445
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.689
Then all tps features from the old Tails version are active 1.214
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.641
And the expected persistent files created with the old Tails version are present in the filesystem 0.932
And all persistent directories from the old Tails version have safe access rights 1.664
After features/support/hooks.rb:339 0.715
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:40.341
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.851
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.034
And Tor is ready 13.708
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.010
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.032
Given I shutdown Tails and wait for the computer to power off 6.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.106
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.658
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.211
When the network is plugged 0.027
And Tor is ready 10.436
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.901
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.881
Given I shutdown Tails and wait for the computer to power off 2.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.164
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 10.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.026
And Tor is ready 11.200
Then the Upgrader considers the system as up-to-date 0.086
# 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.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 1.001
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.095
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.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 8.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.265
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.000