Project Number Date
test_Tails_ISO_post-rm-7.11 6 20 Aug 2026, 16:31

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:8.373 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:19.036
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.168
When I start Tails from USB drive "old" with network unplugged 1:0.701
Then the boot device has safe access rights 2.472
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.148
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.511
After features/support/hooks.rb:108 0.057
Tags: @product
1:26.997
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 51.194
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 24.045
And I take note of which tps features are available 6.730
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 4.063
After features/support/hooks.rb:339 0.344
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.983
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.907
When I write some files expected to persist 1.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.744
And I take note of which tps features are available 6.615
And I shutdown Tails and wait for the computer to power off 3.989
# 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.146
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.012
Tags: @product
2:16.221
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 9.183
And I log in to a new session 12.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.718
And I plug USB drive "to_upgrade" 2.305
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.610
Then the running Tails is installed on USB drive "to_upgrade" 19.855
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 3.654
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.129
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.446
Then all tps features from the old Tails version are active 1.328
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.148
And all persistent directories from the old Tails version have safe access rights 2.007
After features/support/hooks.rb:339 0.927
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
3:55.086
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 21.366
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
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.373
When the network is plugged 0.029
And Tor is ready 12.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.616
Given I shutdown Tails and wait for the computer to power off 5.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.872
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 7.203
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.218
When the network is plugged 0.025
And Tor is ready 10.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.278
Given I shutdown Tails and wait for the computer to power off 4.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.384
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.599
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.021
And Tor is ready 9.539
Then the Upgrader considers the system as up-to-date 10.433
# 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.226
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.432
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.045
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.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.529
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.998
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.000