Project Number Date
test_Tails_ISO_devel 4076 16 Nov 2025, 12:44

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 15:33.345 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:47.511
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.910
When I start Tails from USB drive "old" with network unplugged 1:11.534
Then the boot device has safe access rights 2.888
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 3.828
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:23.270
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 28.724
And I take note of which tps features are available 1.332
Then a Tails persistence partition exists on USB drive "old" 0.689
And I shutdown Tails and wait for the computer to power off 7.607
After features/support/hooks.rb:331 0.433
After features/support/hooks.rb:100 0.011
Tags: @product
2:9.135
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.743
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.868
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.517
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 7.767
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.118
After features/support/hooks.rb:331 0.339
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.100
And I log in to a new session 14.844
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.240
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.823
Then the running Tails is installed on USB drive "to_upgrade" 20.431
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 3.761
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.487
Then all tps features from the old Tails version are active 1.469
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.249
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.159
After features/support/hooks.rb:331 0.937
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:50.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.305
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.050
And Tor is ready 15.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.498
Given I shutdown Tails and wait for the computer to power off 10.966
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.174
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
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.154
# 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.308
When the network is plugged 0.057
And Tor is ready 10.456
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.106
Given I shutdown Tails and wait for the computer to power off 8.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.134
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.368
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.190
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.050
And Tor is ready 10.780
Then the Upgrader considers the system as up-to-date 0.246
# 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 5.242
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:331 1.092
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
23.323
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 11.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.000