# README
Assertion
If you intend to introduce a new assertion, please follow this approach:
- We want to avoid writing generic assertions, that are specific to certain tests. Assertions should contain no custom logic, and instead support dependency injection.
- If you are unsure if an assertion is generic, start by adding it directly to your test, and then you can make it more generic in a follow-up.
Conventions
Contextual Assertions
Some assertions provided in this package may consider the Gloo Gateway context for conditional logic based on metadata about the installation being asserted against. One example is asserting behavior differently if the validating webhook is installed and configured to reject certain resources.
Well Known Manifests
Additionally, some assertions may rely on well-known strings in the manifest filenames for conditional logic. As mentioned above, an example is asserting behavior differently if a manifest is expected to be rejected by the validating webhook.
# Functions
NewProvider returns a Provider that will provide Assertions that can be executed against an installation of Gloo Gateway.
# Constants
No description provided by the author
WebhookReject is a well-known string that should be placed in the filename of any manifest which should be rejected by the Gloo Gateway validating webhook if it is enabled and configured to reject on errors.