| name | home-assistant-testing |
| description | Run a disposable Home Assistant container against this repository's custom component and verify the integration through the real UI with Playwright. Use when testing Home Assistant config flows, entity creation, onboarding, or end-to-end behavior of `custom_components/`. |
Home Assistant Testing
Purpose
Use this skill to validate the custom integration end to end in a throwaway Home Assistant instance.
Quick Start
- Use the reusable files in
resources/home-assistant-test/.
- Start the container with Docker, mounting:
resources/home-assistant-test/config to /configcustom_components to /config/custom_components
- Wait for Home Assistant to finish booting on
http://127.0.0.1:8123.
- Use the Playwright MCP browser tools to:
- complete onboarding if needed
- open Devices & Services
- add the custom integration
- enter credentials in the UI instead of storing them in files
- Inspect logs and created entities before concluding the test.
Container Workflow
Run the harness from the repository root:
docker compose -f resources/home-assistant-test/docker-compose.yml up -d
Stop and clean up when done:
docker compose -f resources/home-assistant-test/docker-compose.yml down
Validation Checklist
Notes
- Prefer the real Home Assistant UI over direct file-based config when validating config flow behavior.
- Do not commit credentials or place them in
configuration.yaml.
- If the browser MCP cannot launch because of a local Chrome conflict, resolve that before continuing UI automation.
- Keep this skill focused on disposable local testing; do not reuse the container as a long-lived development environment.
