Project Number Date
test_Tails_ISO_devel 4102 05 Dec 2025, 23:14

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 16:0.377 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.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.293
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 33.741
When I start Tails from USB drive "old" with network unplugged 1:12.995
Then the boot device has safe access rights 3.137
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.215
And process "udev-watchdog" is running 0.168
And udev-watchdog is monitoring the correct device 0.533
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 3.839
After features/support/hooks.rb:100 0.021
Tags: @product
2:13.412
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:29.895
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.808
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.906
After features/support/hooks.rb:331 0.702
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.570
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.979
Then Tails is running from USB drive "old" 0.719
And all tps features are active 2.241
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 2.595
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 3.186
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.216
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.274
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 11.603
And I log in to a new session 17.474
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.692
And I plug USB drive "to_upgrade" 2.596
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.108
Then the running Tails is installed on USB drive "to_upgrade" 22.268
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.312
After features/support/hooks.rb:331 3.899
After features/support/hooks.rb:100 0.000
Tags: @product
1:35.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.411
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:25.457
Then all tps features from the old Tails version are active 2.194
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.302
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:331 0.984
After features/support/hooks.rb:100 0.042
4:53.702
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 14.242
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.059
And Tor is ready 16.587
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.955
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.446
Given I shutdown Tails and wait for the computer to power off 11.756
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.679
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.506
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
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.145
# 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.339
When the network is plugged 5.497
And Tor is ready 10.238
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.562
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.563
Given I shutdown Tails and wait for the computer to power off 8.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.466
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.322
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.203
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.493
When the network is plugged 0.196
And Tor is ready 23.797
Then the Upgrader considers the system as up-to-date 0.153
# 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.867
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.578
After features/support/hooks.rb:331 1.095
After features/support/hooks.rb:100 0.019
28.145
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 14.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 11.790
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.831
After features/support/hooks.rb:331 1.721
After features/support/hooks.rb:100 0.000