Add unit/integration tests for Security Policies features to verify multiple and older policy.yml configurations
Summary
Timebox: 4 days
In scope of this issue we would like to improve our backend unit/integration tests to ensure we are verifying if our features are also working for current and past policy.yml
configuration. This is crucial to understand if we are not introducing any breaking changes, so we can catch them and fail early.
Improvements
- FactoryBot factories - add ability to generate multiple different
policy.yml
configuration with and without fields in YAML, we need to ensure that all valid configurations (validated with JSON schema) are supported in our services, - GraphQL API tests - all valid
policy.yml
file configuration should be loaded normally without 500 error - perhaps we could somehow generate many configs from JSON Schema, and test if they are not producing any 500 errors or exceptions, - etc.
Risks
No risks, only benefits - better test coverage = better verification.
Involved components
TBD
Edited by Alan (Maciej) Paruszewski