Project Number Date
test_Tails_ISO_devel 4073 14 Nov 2025, 10:26

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 17:1.657 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
2:15.364
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.627
When I start Tails from USB drive "old" with network unplugged 1:37.326
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 3.971
After features/support/hooks.rb:100 0.012
Tags: @product
2:7.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:27.532
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 29.662
And I take note of which tps features are available 1.144
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 7.799
After features/support/hooks.rb:331 0.640
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.839
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.282
When I write some files expected to persist 1.682
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.650
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 7.704
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.015
After features/support/hooks.rb:331 0.561
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.192
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.478
And I log in to a new session 19.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.262
And I plug USB drive "to_upgrade" 3.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.418
Then the running Tails is installed on USB drive "to_upgrade" 20.852
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:331 3.892
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.112
Then all tps features from the old Tails version are active 1.533
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 3.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.722
And all persistent directories from the old Tails version have safe access rights 2.434
After features/support/hooks.rb:331 0.776
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
5:14.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.403
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.098
And Tor is ready 15.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.639
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.522
Given I shutdown Tails and wait for the computer to power off 11.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.445
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.293
When the network is plugged 0.085
And Tor is ready 11.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.146
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.270
Given I shutdown Tails and wait for the computer to power off 8.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.048
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.381
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.759
And Tor is ready 12.210
Then the Upgrader considers the system as up-to-date 0.195
# 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 5.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.640
After features/support/hooks.rb:331 1.345
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
25.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.561
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.929
After features/support/hooks.rb:331 0.890
After features/support/hooks.rb:100 0.000