local-test

Build, run, and validate IronClaw locally with Docker and Chrome MCP.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Adityashandilya555/iron --skill local-test-adityashandilya555
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-test
Source: https://github.com/Adityashandilya555/iron/tree/main/skills/local-test
Command: npx skills add https://github.com/Adityashandilya555/iron --skill local-test-adityashandilya555

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.

Core Features & Use Cases

  • Local build and test workflow using a Docker-based environment to mimic production.
  • Chrome MCP browser automation for UI workflow verification and rapid iteration.
  • Reproducible test environment, enabling quick validation of changes before deployment.

Quick Start

Start a local test container with the provided Docker setup and access the web gateway to run UI tests.

Frequently Asked Questions about local-test

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

FAQPage Schema
How do I run local UI testing with Docker and Chrome MCP?

Local UI testing with Docker and Chrome MCP involves building a Docker container to mimic production and using Chrome MCP browser automation to verify UI workflows. This provides a reproducible environment for validating feature changes locally.

What is Chrome MCP used for in a local dev environment?

Chrome MCP in a local dev environment is used for browser automation to execute UI workflow tests. It enables rapid iteration and verification of web gateway interactions within a controlled Docker container setup.

How do I build and validate IronClaw locally before deployment?

To build and validate IronClaw locally, you start a local test container using the provided Docker setup. You then access the web gateway to run and validate UI workflows via Chrome MCP browser automation.

Do I need Docker to run local browser automation tests?

Yes, Docker is required to run these local browser automation tests. The Skill relies on Docker containers to establish a reproducible test environment that mimics production for accurate UI workflow verification.

Can I use this setup for repeatable local test environments?

Yes, you can use this Docker and Chrome MCP setup for repeatable local test environments. The containerized approach ensures consistent state across test runs, enabling quick validation of changes before deployment.

What are the limitations of local Docker testing with Chrome MCP?

Local Docker testing with Chrome MCP is limited to browser-based UI workflow verification and requires both Docker and Chrome MCP tooling installed. It focuses on local validation rather than scaling for production-level load testing.