Project Number Date
test_Tails_ISO_devel 4493 14 Jul 2026, 11:17

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:23.610 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
57.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
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.172
When I start Tails from USB drive "old" with network unplugged 39.692
Then the boot device has safe access rights 2.737
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:339 3.683
After features/support/hooks.rb:108 0.012
Tags: @product
1:28.355
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login 51.184
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 24.258
And I take note of which tps features are available 4.205
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 7.869
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.953
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.808
Then Tails is running from USB drive "old" 0.264
And all tps features are active 4.650
When I write some files expected to persist 1.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 2.009
And I take note of which tps features are available 3.612
And I shutdown Tails and wait for the computer to power off 7.895
# 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.992
After features/support/hooks.rb:339 0.328
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.505
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.093
And I log in to a new session 11.464
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.803
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.422
Then the running Tails is installed on USB drive "to_upgrade" 14.211
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.991
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.547
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.042
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.845
Then all tps features from the old Tails version are active 0.852
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.565
And the expected persistent files created with the old Tails version are present in the filesystem 1.096
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:339 0.698
After features/support/hooks.rb:108 0.005
3:46.200
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.847
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.018
And Tor is ready 11.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.907
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.181
Given I shutdown Tails and wait for the computer to power off 9.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.150
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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 1.193
When the network is plugged 0.018
And Tor is ready 9.693
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.983
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.588
Given I shutdown Tails and wait for the computer to power off 8.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.057
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.670
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.031
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.013
And Tor is ready 10.568
Then the Upgrader considers the system as up-to-date 10.500
# 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.668
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.430
After features/support/hooks.rb:339 0.686
After features/support/hooks.rb:108 0.021
18.619
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.658
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.000