Lines Matching full:covered
137 Object management tests verify that the driver is able to create and destroy objects of all types. The tests don't attempt to use the objects (unless necessary for testing object construction) as that is covered by feature-specific tests. For all object types the object management tests cover:
297 Pipeline layouts will be covered mostly by tests that use various layouts, but in addition some corner-case tests are needed:
478 ** Sampling verification with nearest only (other modes will be covered separately)
520 Shader API test will verify that shader loading functions behave as expected. Verifying that various SPIR-V constructs are accepted and executed correctly however is not an objective; that will be covered more extensively by a separate SPIR-V test set.
674 Draw command tests verify that all draw parameters are respected (including vertex input state) and various draw call sizes work correctly. The tests won't however validate that all side effects of shader invocations happen as intended (covered by feature-specific tests) nor that primitive rasterization is fully correct (will be covered by separate targeted tests).
681 NOTE: Assuming that compute-specific shader features, such as shared memory access, is covered by SPIR-V tests.