skills.rest
chtugha
chtughaCOMMUNITY
Explore all skills by this author →
GitHub

local-test

Automate local testing of BrassClaw's web gateway with Docker and Chrome MCP.

Updated May 7, 2026
Search Tags:#browser automation#docker#local testing#web gateway#BrassClaw
One-click install
npx skills add https://github.com/chtugha/brassclaw --skill local-test-chtugha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-test
Source: https://github.com/chtugha/brassclaw/tree/main/skills/local-test
Command: npx skills add https://github.com/chtugha/brassclaw --skill local-test-chtugha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a local testing environment for BrassClaw using Docker containers and Chrome MCP browser automation, enabling users to test web gateway changes without the need for cloud infrastructure.

Core Features & Use Cases

  • Local Docker Testing: Build and run BrassClaw locally with Docker containers.
  • Chrome MCP Automation: Utilize Chrome MCP for browser automation and UI testing.
  • Use Case: If you are developing or modifying the BrassClaw web gateway, you can use this Skill to test your changes locally before deploying them to production.

Quick Start

Run the following command to build the test image and start the container on port 3003:

docker build --platform linux/amd64 -f Dockerfile.test -t brassclaw-test .
docker run --rm -p 3003:3003 \
  -e ONBOARD_COMPLETED=true \
  -e CLI_ENABLED=false \
  -e NEARAI_API_KEY=<key> \
  brassclaw-test

Frequently Asked Questions about local-test

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

FAQPage Schema
How do I test a web gateway locally without using cloud infrastructure?▼

To test a web gateway locally without cloud infrastructure, you can use Docker containers combined with Chrome MCP browser automation. This approach builds and runs the gateway environment isolated on your machine, enabling UI testing without remote deployments.

What is Chrome MCP browser automation used for in local Docker testing?▼

Chrome MCP browser automation drives UI interactions against a locally running Docker container. It automates web page navigation and element verification, allowing developers to validate web gateway changes before production deployment.

Do I need Docker and Chrome installed to run local browser automation tests?▼

Yes, Docker and Chrome with MCP browser automation tools are required. Docker builds and isolates the test container, while Chrome MCP executes the browser automation needed to validate web UI changes locally.

How do I build and run a local Docker container for web UI testing?▼

Build the Docker image using a Dockerfile.test with the linux/amd64 platform, then run the container mapping port 3003. Pass necessary environment variables like API keys to start the local testing gateway successfully.

Can I test web UI changes locally without deploying to production?▼

Yes, you can test web UI changes locally by running a Docker container with the appropriate environment variables. This setup replicates the gateway environment on your machine, allowing safe validation before any production deployment.

Related Skills

Explore More Software Engineering Skills→
wdappwdapp

local-test

Automate Docker container creation for local IronClaw web gateway testing.

Community
Intermediate
adolfosalasgomez3011adolfosalasgomez3011

webapp-testing

Automate local web application testing with Playwright scripts.

Community
Intermediate
faustellar1995faustellar1995
1

local-test

Build, deploy, and test IronClaw web gateway changes locally with Docker and Chrome MCP.

Community
Intermediate
mahg-esmahg-es
3

cloud-deploy

Provision cloud infrastructure with Terraform, Pulumi, or CloudFormation.

Official
Advanced