Automation Testing

How automated tests validate Guardian services, APIs, and user interfaces.

Automation testing verifies that Guardian code changes preserve expected behavior. It runs repeatable checks before changes are released.

This article covers automated checks for the Guardian codebase. It does not cover policy authoring tests.

Guardian combines services, APIs, and user interfaces. A change in one component can affect another component.

Manual checks are slow and inconsistent. Automated tests detect regressions early and provide repeatable release feedback.

The codebase uses focused unit tests and end-to-end suites. Unit tests validate service behavior in isolation.

End-to-end tests exercise workflows across the running application. The e2e-tests directory contains Cypress-based UI and API automation.

These suites verify API responses, user interactions, and cross-service behavior. They support development and release validation.

Automation testing validates the Guardian codebase and its integrations. It tests whether application changes behave correctly.

Policy Integrity Tests validate declared policy inputs and outputs. They test a policy's behavior, not the Guardian codebase.

Dry Run mode simulates policy execution without affecting live systems. It supports safe workflow testing with virtual users and local artifacts.

Automation suites can use dry-run scenarios when validating policy flows. Dry Run mode is not the codebase test framework.

Was this helpful?