Project Number Date
test_Tails_ISO_devel 4368 30 Apr 2026, 11:07

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:25.313 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:1.702
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.629
When I start Tails from USB drive "old" with network unplugged 43.534
Then the boot device has safe access rights 2.710
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 1.287
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.334
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 55.162
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.217
And I take note of which tps features are available 0.731
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 8.218
After features/support/hooks.rb:331 0.548
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.953
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.545
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.224
When I write some files expected to persist 1.393
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.603
And all persistent directories from the old Tails version have safe access rights 1.924
And I take note of which tps features are available 0.202
And I shutdown Tails and wait for the computer to power off 4.114
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.255
After features/support/hooks.rb:331 0.408
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.347
And I log in to a new session 11.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.457
And I plug USB drive "to_upgrade" 2.331
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.829
Then the running Tails is installed on USB drive "to_upgrade" 16.016
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.033
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.783
Then all tps features from the old Tails version are active 1.292
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 2.750
And the expected persistent files created with the old Tails version are present in the filesystem 1.297
And all persistent directories from the old Tails version have safe access rights 2.033
After features/support/hooks.rb:331 0.676
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:36.087
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.365
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.016
And Tor is ready 20.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.445
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.495
Given I shutdown Tails and wait for the computer to power off 20.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.080
Then Tails is running version 6.2~testoverlayfs 0.039
And all tps features are active 1.416
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# 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.218
When the network is plugged 0.016
And Tor is ready 21.198
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.574
Given I shutdown Tails and wait for the computer to power off 13.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.235
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.247
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.017
And Tor is ready 21.023
Then the Upgrader considers the system as up-to-date 0.120
# 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.881
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 0.905
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
25.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.453
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.044
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 17.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.000