facility-locator-tests

To run Cypress tests for a facility-locator app, you must configure the environment with APP_FOLDER=facility-locator and ENTRY_NAME=facilities. This setup executes the complete test suite, covering 53 unit test files and 20 E2E specs.

Automating facility-locator test coverage in a CI pipeline requires Node.js and Yarn installed in the environment. You must also set the correct app configuration variables, APP_FOLDER and ENTRY_NAME, to validate tests and generate reliable reporting.

Yes, the facility-locator Cypress test suite includes prerequisite validation to verify required tooling like Node and Yarn. It checks for the correct app configuration before executing the unit and E2E tests to ensure reliable results.

Yes, you can run facility-locator Cypress tests locally by starting the development server with entry=facilities. Once the server runs, execute the unit and E2E test commands to validate your code changes locally before pushing to CI.

Facility-locator Cypress tests fail if the environment lacks required tooling like Node.js and Yarn. Incorrect app configuration, specifically missing the fixed APP_FOLDER=facility-locator and ENTRY_NAME=facilities variables, also causes test execution failures.

Setting APP_FOLDER to facility-locator and ENTRY_NAME to facilities ensures the Cypress test runner targets the correct application path. This fixed configuration orchestrates consistent unit and E2E test coverage and accurate results reporting across CI pipelines.