Project Number Date
test_Tails_ISO_devel 4497 16 Jul 2026, 11:11

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:24.609 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
58.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.046
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" 13.319
When I start Tails from USB drive "old" with network unplugged 41.186
Then the boot device has safe access rights 2.489
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.422
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.191
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 23.911
And I take note of which tps features are available 3.757
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.160
Then Tails is running from USB drive "old" 0.213
And all tps features are active 4.475
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.794
And I take note of which tps features are available 3.737
And I shutdown Tails and wait for the computer to power off 8.213
# 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.523
After features/support/hooks.rb:339 0.488
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.299
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 7.712
And I log in to a new session 12.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.668
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.121
Then the running Tails is installed on USB drive "to_upgrade" 14.743
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.062
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.185
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:3.460
Then all tps features from the old Tails version are active 0.990
And Tails is running from USB drive "to_upgrade" 0.189
And the boot device has safe access rights 2.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 1.918
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:42.561
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 with a persistent partition enabled and logged in 7.926
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.018
And Tor is ready 12.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.161
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.577
Given I shutdown Tails and wait for the computer to power off 5.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.842
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.790
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.188
When the network is plugged 0.013
And Tor is ready 10.534
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.561
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.913
Given I shutdown Tails and wait for the computer to power off 7.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.135
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.703
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.014
And Tor is ready 9.688
Then the Upgrader considers the system as up-to-date 10.506
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.215
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.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 11.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.677
After features/support/hooks.rb:339 0.993
After features/support/hooks.rb:108 0.000