Project Number Date
test_Tails_ISO_devel 4570 26 Aug 2026, 14:15

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:40.665 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:1.981
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.984
When I start Tails from USB drive "old" with network unplugged 44.220
Then the boot device has safe access rights 1.988
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.689
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.355
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 47.872
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 23.586
And I take note of which tps features are available 6.494
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 2.583
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.693
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.603
Then Tails is running from USB drive "old" 0.234
And all tps features are active 7.360
When I write some files expected to persist 1.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.601
And I take note of which tps features are available 6.677
And I shutdown Tails and wait for the computer to power off 3.955
# 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.596
After features/support/hooks.rb:339 0.128
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.713
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.664
And I log in to a new session 13.395
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.935
Then the running Tails is installed on USB drive "to_upgrade" 19.497
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 3.468
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.239
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.148
Then all tps features from the old Tails version are active 1.368
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.640
And the expected persistent files created with the old Tails version are present in the filesystem 0.996
And all persistent directories from the old Tails version have safe access rights 1.699
After features/support/hooks.rb:339 0.950
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:51.687
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.394
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.043
And Tor is ready 12.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.593
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.025
Given I shutdown Tails and wait for the computer to power off 5.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.397
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# 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.225
When the network is plugged 0.040
And Tor is ready 10.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.985
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.775
Given I shutdown Tails and wait for the computer to power off 4.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.587
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.742
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.030
And Tor is ready 9.994
Then the Upgrader considers the system as up-to-date 10.511
# 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.551
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 0.776
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
18.993
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.495
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 9.179
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.967
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.000