test-acceptance

Acceptance tests can run with environment pre-checks that verify backend API and frontend UI availability from infrastructure environment files before executing. This ensures required services are running and healthy, preventing false test failures caused by unavailable dependencies.

Yes, targeted test execution supports running a specific test class rather than the full suite. You can specify whether to run all backend tests, all frontend tests, or a single acceptance test class, significantly speeding up validation for UI regressions or individual API scenarios.

A stop-on-first-failure strategy halts acceptance test execution at the first error encountered. This allows you to detect compilation, infrastructure, or application issues early and immediately inspect the root cause without waiting for the remaining test suite to finish.

Service health verification is performed by reading required ports from infrastructure environment files and checking backend and frontend availability before launching the acceptance test script. This confirms that necessary application services are operational prior to test execution.

Yes, the acceptance testing workflow operates with Gradle to run end-to-end validation. It monitors background execution of the acceptance test script and applies a stop-on-first-failure workflow to efficiently manage test runs for both backend APIs and frontend UIs.

Acceptance tests often fail due to unavailable backend or frontend services. Using environment readiness checks verifies service availability from infrastructure settings before execution, ensuring the required app services are running so you only test actual application regressions.