Project Number Date
test_Tails_ISO_devel 4057 06 Nov 2025, 09:48

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 17:8.662 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:52.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 34.644
When I start Tails from USB drive "old" with network unplugged 1:12.048
Then the boot device has safe access rights 3.908
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.105
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:331 4.470
After features/support/hooks.rb:100 0.013
Tags: @product
2:9.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:27.861
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 30.726
And I take note of which tps features are available 1.473
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 8.009
After features/support/hooks.rb:331 0.528
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:44.737
Then Tails is running from USB drive "old" 0.696
And all tps features are active 2.460
When I write some files expected to persist 1.550
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 2.407
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 7.786
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.728
After features/support/hooks.rb:331 0.418
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.537
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 20.717
And I log in to a new session 19.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.792
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:2.360
Then the running Tails is installed on USB drive "to_upgrade" 21.578
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 4.042
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.353
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 4.184
And the expected persistent files created with the old Tails version are present in the filesystem 1.759
And all persistent directories from the old Tails version have safe access rights 2.650
After features/support/hooks.rb:331 0.985
After features/support/hooks.rb:100 0.012
5:17.304
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 with a persistent partition enabled and logged in 12.916
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.689
When the network is plugged 0.070
And Tor is ready 14.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.809
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.809
Given I shutdown Tails and wait for the computer to power off 11.774
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.831
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.945
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.224
# 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.328
When the network is plugged 0.059
And Tor is ready 12.356
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.313
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.945
Given I shutdown Tails and wait for the computer to power off 7.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.050
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.755
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.262
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.061
And Tor is ready 12.533
Then the Upgrader considers the system as up-to-date 0.205
# 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 6.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.569
After features/support/hooks.rb:331 1.450
After features/support/hooks.rb:100 0.040
26.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.949
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 12.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.797
After features/support/hooks.rb:331 1.082
After features/support/hooks.rb:100 0.000