Project Number Date
test_Tails_ISO_21461-update-chutney 12 02 Aug 2026, 22: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 11:16.664 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.770
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.154
When I start Tails from USB drive "old" with network unplugged 43.322
Then the boot device has safe access rights 2.500
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.795
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 51.836
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 24.120
And I take note of which tps features are available 3.815
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 4.061
After features/support/hooks.rb:339 0.252
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.308
Then Tails is running from USB drive "old" 0.222
And all tps features are active 4.677
When I write some files expected to persist 1.345
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.900
And I take note of which tps features are available 3.541
And I shutdown Tails and wait for the computer to power off 4.040
# 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.839
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.007
Tags: @product
2:8.154
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 7.688
And I log in to a new session 11.933
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.818
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.212
Then the running Tails is installed on USB drive "to_upgrade" 13.956
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.033
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.136
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.643
Then all tps features from the old Tails version are active 0.943
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 2.371
And the expected persistent files created with the old Tails version are present in the filesystem 1.157
And all persistent directories from the old Tails version have safe access rights 1.760
After features/support/hooks.rb:339 0.613
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.247
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.100
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.273
When the network is plugged 0.020
And Tor is ready 13.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.791
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.502
Given I shutdown Tails and wait for the computer to power off 8.103
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.936
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.785
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.222
When the network is plugged 0.014
And Tor is ready 10.704
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.583
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.888
Given I shutdown Tails and wait for the computer to power off 4.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.812
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.768
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.015
And Tor is ready 9.580
Then the Upgrader considers the system as up-to-date 10.653
# 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.254
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.472
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.320
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.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.076
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.000