facility-locator-tests

Run facility-locator unit and E2E tests with Cypress.

Updated Oct 28, 2025

Search Tags:#automation #testing #e2e #unit-testing #cypress #ci #facility-locator

Ready to run

npx skills add https://github.com/SnowboardTechie/dotfiles --skill facility-locator-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: facility-locator-tests
Source: https://github.com/SnowboardTechie/dotfiles/tree/main/dot-config/opencode/skills/facility-locator-tests
Command: npx skills add https://github.com/SnowboardTechie/dotfiles --skill facility-locator-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the full facility-locator test suite (unit and E2E) by orchestrating Cypress tests with a fixed APP_FOLDER and ENTRY_NAME to ensure consistent coverage and reporting.

Core Features & Use Cases

Unit and E2E Coverage: Runs both unit tests (53 files) and E2E tests (20 specs) for facility-locator.
Prerequisite Validation: Verifies required tooling (Node, Yarn) and correct app configuration (APP_FOLDER and ENTRY_NAME) before execution.
Use Case: CI pipelines can automatically validate the facility-locator test suite on changes to vets-website.

Quick Start

Start the development server with entry=facilities and execute the unit and E2E test commands for facility-locator.

Frequently Asked Questions about facility-locator-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run Cypress E2E and unit tests for a facility-locator app?▼

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.

What prerequisites do I need to automate facility-locator test coverage in a CI pipeline?▼

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.

Does the facility-locator Cypress test suite validate tooling before execution?▼

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.

Can I run facility-locator Cypress tests locally before pushing to CI?▼

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.

Why are my facility-locator Cypress tests failing in the CI pipeline?▼

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.

What is the purpose of setting APP_FOLDER and ENTRY_NAME for facility-locator testing?▼

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.