skills.rest
dianlight
dianlightCOMMUNITY
Explore all skills by this author →
GitHub

test-remote-environment

Test SRAT against a live Home Assistant environment with Playwright.

8|1|Updated Dec 9, 2024
Search Tags:#playwright#frontend-backend#ci-cd#e2e-testing#home-assistant#remote-testing#addon-management
One-click install
npx skills add https://github.com/dianlight/srat --skill test-remote-environment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-remote-environment
Source: https://github.com/dianlight/srat/tree/main/.github/skills/test-remote-environment
Command: npx skills add https://github.com/dianlight/srat --skill test-remote-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated validation of SRAT against a real Home Assistant test environment, ensuring the backend, frontend, and addon workflows can be exercised in a safe, end-to-end setting.

Core Features & Use Cases

  • Deploy backend to the test environment with make build_remote, start the frontend with bun dev:remote, and orchestrate the local_sambanas2 addon lifecycle via MCP.
  • Read core and addon logs to verify startup health, error-free operation, and correct integration behavior.
  • Browse and validate the UI at http://localhost:3080/ using Playwright, ensuring end-to-end flows work as expected.

Quick Start

Deploy and test SRAT remotely by building the backend, starting the frontend, and validating the UI at http://localhost:3080.

Frequently Asked Questions about test-remote-environment

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

FAQPage Schema
How do I run end-to-end testing for a Home Assistant addon workflow?▼

You can validate a Home Assistant addon lifecycle by orchestrating addon control via MCP, reading core and addon logs to verify startup health, and verifying UI behavior at http://localhost:3080/ with Playwright.

Can I automate Playwright UI validation against a local development server?▼

Playwright can automate browser interactions against the frontend server at http://localhost:3080/ to verify UI behavior and ensure end-to-end integration flows work correctly.

What is needed to validate backend and frontend integration in a remote test environment?▼

Validating backend and frontend integration requires deploying backend builds via make build_remote, starting the frontend with bun dev:remote, and monitoring core and addon logs to confirm error-free startup.

Does this testing approach support addon lifecycle management through MCP?▼

Yes, addon lifecycle management is supported through MCP, allowing you to orchestrate addon control, verify startup health, and read core and addon logs to ensure correct integration behavior.

What are the limitations of using a live Home Assistant test environment for CI/CD validation?▼

Using a live Home Assistant test environment for CI/CD validation is limited to safe, end-to-end exercising of backend, frontend, and addon workflows without impacting production systems.

Related Skills

Explore More Software Engineering Skills→
komal-SkyNETkomal-SkyNET
772

home-assistant-manager

Automates Home Assistant configuration and Lovelace dashboard deployment via SSH, hass-cli, and git.

Community
Intermediate
CoolCoderSuperCoolCoderSuper
4

integration-test-analysis

Diagnose Visual Studio integration test failures from Azure DevOps CI artifacts.

Community
Advanced
veerababumanyamveerababumanyam

webapp-testing

Automate RawDrive web UI browser tests with Playwright MCP across environments.

Community
Advanced
wtahwtah

integration-testing

Validate container builds, tests, and startup behavior in isolated local environments.

Community
Basic