Project Number Date
test_Tails_ISO_21771-test-reliable-celluloid-open 3 07 Sep 2026, 20:10

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:19.521 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.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.711
When I start Tails from USB drive "old" with network unplugged 48.955
Then the boot device has safe access rights 2.225
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.422
After features/support/hooks.rb:108 0.083
Tags: @product
1:25.461
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.567
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 24.141
And I take note of which tps features are available 6.708
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 4.193
After features/support/hooks.rb:339 0.375
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.218
Then Tails is running from USB drive "old" 0.205
And all tps features are active 7.037
When I write some files expected to persist 1.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.706
And I take note of which tps features are available 6.312
And I shutdown Tails and wait for the computer to power off 2.563
# 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.597
After features/support/hooks.rb:339 0.410
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.280
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.495
And I log in to a new session 10.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.654
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.158
Then the running Tails is installed on USB drive "to_upgrade" 18.654
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.971
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.468
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.242
Then all tps features from the old Tails version are active 1.068
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.155
And the expected persistent files created with the old Tails version are present in the filesystem 0.958
And all persistent directories from the old Tails version have safe access rights 1.713
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.868
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.034
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.033
And Tor is ready 12.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.491
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.017
Given I shutdown Tails and wait for the computer to power off 5.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.286
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 9.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.024
And Tor is ready 10.540
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.882
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.133
Given I shutdown Tails and wait for the computer to power off 2.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.290
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.308
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.036
And Tor is ready 10.151
Then the Upgrader considers the system as up-to-date 10.482
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:339 0.985
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
18.302
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.809
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 8.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.066
After features/support/hooks.rb:339 0.855
After features/support/hooks.rb:108 0.000