Project Number Date
test_Tails_ISO_devel 4319 05 Apr 2026, 07:55

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:25.341 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:0.634
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.157
When I start Tails from USB drive "old" with network unplugged 42.082
Then the boot device has safe access rights 2.646
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 1.272
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.390
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 56.223
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 25.136
And I take note of which tps features are available 0.756
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 4.352
After features/support/hooks.rb:331 0.481
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.281
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.231
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.483
And all persistent directories from the old Tails version have safe access rights 1.849
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 7.914
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.641
After features/support/hooks.rb:331 0.534
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.310
And I log in to a new session 12.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.911
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.894
Then the running Tails is installed on USB drive "to_upgrade" 16.045
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 2.215
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.694
Then all tps features from the old Tails version are active 0.923
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.550
And the expected persistent files created with the old Tails version are present in the filesystem 1.217
And all persistent directories from the old Tails version have safe access rights 2.021
After features/support/hooks.rb:331 0.529
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
4:39.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.608
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.017
And Tor is ready 20.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.654
Given I shutdown Tails and wait for the computer to power off 18.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.774
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
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.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.204
When the network is plugged 0.016
And Tor is ready 22.449
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.071
Given I shutdown Tails and wait for the computer to power off 17.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.255
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.015
And Tor is ready 20.730
Then the Upgrader considers the system as up-to-date 0.117
# 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.269
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.855
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.000