Project Number Date
test_Tails_ISO_stable 6545 29 Jul 2026, 21:34

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:10.749 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:6.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.747
When I start Tails from USB drive "old" with network unplugged 46.264
Then the boot device has safe access rights 3.310
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.536
After features/support/hooks.rb:108 0.018
Tags: @product
1:30.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 56.059
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 25.132
And I take note of which tps features are available 4.187
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 4.023
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.021
Tags: @product
1:40.509
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.227
Then Tails is running from USB drive "old" 0.268
And all tps features are active 4.765
When I write some files expected to persist 1.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 2.143
And I take note of which tps features are available 4.632
And I shutdown Tails and wait for the computer to power off 4.312
# 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.283
After features/support/hooks.rb:339 0.312
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.501
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 8.595
And I log in to a new session 12.996
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.023
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.798
Then the running Tails is installed on USB drive "to_upgrade" 16.574
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.069
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.927
Then all tps features from the old Tails version are active 1.076
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.699
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.147
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:2.132
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 7.844
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.051
And Tor is ready 14.347
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.952
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.619
Given I shutdown Tails and wait for the computer to power off 7.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.801
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.920
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.226
When the network is plugged 0.013
And Tor is ready 9.792
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.191
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.153
Given I shutdown Tails and wait for the computer to power off 4.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.201
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.901
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.023
And Tor is ready 9.881
Then the Upgrader considers the system as up-to-date 10.732
# 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.252
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.533
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 7.962
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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.014
And Tor is ready 10.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.612
After features/support/hooks.rb:339 0.699
After features/support/hooks.rb:108 0.000