Module validation

Modules§

ComponentSpecValidator: Validates that the component meets the requirements of the Component Specification.
ComponentTestCaseConfig: Component configuration for a test case.
ExternalResource: An external resource associated with a component.
HttpResourceConfig: An HTTP resource.
RunnerMetrics: Input and Output runners populate this structure as they send and receive events. The structure is passed into the validator to use as the expected values for the metrics that the components under test actually output.
TestCase: A validation test case.
ValidatableComponentDescription: Description of a validatable component.
ValidationConfiguration: Configuration for validating a component.

ComponentConfiguration: Component type-specific configuration.
ComponentMetricType
ComponentType: Component types that can be validated.
ResourceCodec: The codec used by the external resource.
ResourceDefinition: A resource definition.
ResourceDirection: Direction that the resource is operating in.
StandardValidators: Standard component validators.
TestCaseExpectation: Expected outcome of a validation test case.
TestEvent: An event used in a test case. It is important to have created the event with all fields, immediately after deserializing from the test case definition yaml file. This ensures that the event data we are using in the expected/actual metrics collection is based on the same event. Namely, one issue that can arise from creating the event from the event data twice (once for the expected and once for actual), it can result in a timestamp in the event which may or may not have the same millisecond precision as it’s counterpart.