This directory contains the manifest fragments that are required for running Fuchsia tests hermetically. Tests start from minimum.shard.test-cml and add additional capabilities as necessary by providing the additional_manifest_fragments argument. Some fragments are explained in detail below:
Runs an archivist-without-attribution with custom protocol routing for tests that want to intercept events written to a LogSink by a component.
Runs tests in the chromium test realm, which is mostly hermetic but has access to specific system services that cannot (currently) be faked. For more information, see https://fxbug.dev/91934. This is generally required for all Chromium tests not using the chromium_system_test_facet.
For tests that test fonts by providing fuchsia.fonts.Provider. This shard runs an isolated font provider, but serves the fonts present on the system.
For tests that use the fonts in //third_party/test_fonts by way of //skia:test_fonts_cfv2.
Required by tests that execute JavaScript. Should only be required in a small number of tests.
Capabilities required by anything that uses //base/test when running in the (default) chromium test realm. It is the default base fragment for most test() Components.
The system-wide config-data directory capability is routed to tests running in the realm so that individual tests may route subdirectories as needed. TODO(crbug.com/1360077): Remove this after migrating to the new mechanism.
For tests that test logging functionality by providing fuchsia.logger.Log.
For tests that depend on the sysmem service (e.g. to allocate image buffers to share with Vulkan and Scenic).
Capabilities required by anything that uses //base/test when running as a system test in the chromium-system test realm. It is the base fragment for test() Components that use the chromium_system_test_facet.
Most tests use the minimum shard.
Runs tests in the chromium-system test realm. This is required for Chromium tests that are intended to run against the actual system and its real system services. This is required for, for example, performance tests intended to measure system performance. Another overlapping use case is tests that need to be run in environments without access to the packages containing fake implementations of required protocols that other tests use. (https://crbug.com/1408597 should make that use case obsolete.)
Most tests should use the chromium_test_facet.
For tests that need an isolated UI subsystem, that supports the Flatland API set. This allows tests to e.g. run with view-focus unaffected by any other tests running concurrently on the device, as well as providing test-only functionality such as input-injection support.
For tests that need an isolated display subsystem supporting the legacy Scenic/GFX APIs.
The following fragments are specific to WebEngine functionality as documented documentation at https://fuchsia.dev/reference/fidl/fuchsia.web#CreateContextParams and https://fuchsia.dev/reference/fidl/fuchsia.web#ContextFeatureFlags. Any test-specific exceptions are documented for each file.
Required by tests that need to enable audio output.
Required by tests that need accelerated (e.g., hardware) video codecs. A private (semi-isolated) instance of codec_factory is run for tests using this shard in support of running on system images that don't run it.
For tests that need access to network services, including those that access a local HTTP server.
Corresponds to the NETWORK flag. Required for enabling network access. Note that access to the root SSL certificates is not needed if ContextProvider is used to launch the Context. The fuchsia.device.NameProvider dependency comes from fdio.
Services that are needed to render web content in a Scenic view and present it. Most services are required per the FIDL documentation.
Contains services that need to be present when creating a fuchsia.web.Context. Note that the fuchsia.scheduler.ProfileProvider service is only used in tests that encounter memory pressure code.