cpp-test-authoring

To write automated UI tests for HMCTS CPP, you author Serenity BDD and Cucumber feature files within the cpp-ui-e2e-serenity repository. This process coordinates test creation and validation to ensure adherence to established coding conventions.

Creating Gherkin feature files for HMCTS E2E tests involves defining UI scenarios using Cucumber syntax within the Serenity BDD framework. This ensures new test assets integrate quickly with established patterns in the Crime Common Platform repositories.

Authoring API tests for HMCTS platforms requires coding JUnit 5 and REST Assured tests within the CPP API tests repository. This ensures your test assets follow established patterns and integrate seamlessly with existing validation checks.

Yes, writing tests for the Crime Common Platform requires prior knowledge of Serenity BDD, Cucumber, REST Assured, JUnit 5, and HMCTS coding conventions. The framework assumes you understand these technologies to guide test asset creation effectively.

Automated tests are validated before committing by checking the test code for sensitive data and ensuring strict adherence to HMCTS coding conventions. This pre-commit validation prevents integration issues and maintains repository consistency.

Yes, you can integrate new automated test assets into existing HMCTS repositories using a step-by-step checklist. This quick integration process ensures new UI and API tests align with established patterns and pass pre-commit validation.