Project Number Date
test_Tails_ISO_devel 4530 04 Aug 2026, 14:15

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:39.699 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:5.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
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" 13.573
When I start Tails from USB drive "old" with network unplugged 46.937
Then the boot device has safe access rights 2.846
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:339 3.454
After features/support/hooks.rb:108 0.008
Tags: @product
1:28.022
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 54.083
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.725
And I take note of which tps features are available 4.309
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 4.033
After features/support/hooks.rb:339 0.412
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.553
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.924
Then Tails is running from USB drive "old" 0.248
And all tps features are active 5.379
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 1.746
And I take note of which tps features are available 3.756
And I shutdown Tails and wait for the computer to power off 4.057
# 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.621
After features/support/hooks.rb:339 0.279
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.647
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.718
And I log in to a new session 12.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.305
Then the running Tails is installed on USB drive "to_upgrade" 15.669
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.125
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.811
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.284
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.109
And all persistent directories from the old Tails version have safe access rights 1.811
After features/support/hooks.rb:339 1.033
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:43.855
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.963
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.031
And Tor is ready 13.219
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.775
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.593
Given I shutdown Tails and wait for the computer to power off 6.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.205
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.196
When the network is plugged 0.015
And Tor is ready 10.848
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.991
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.228
Given I shutdown Tails and wait for the computer to power off 4.067
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.895
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 4.531
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.013
And Tor is ready 11.038
Then the Upgrader considers the system as up-to-date 10.639
# 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.222
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 1.064
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
20.671
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.759
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.594
After features/support/hooks.rb:339 0.514
After features/support/hooks.rb:108 0.000