local-test

Automate Docker container creation for local IronClaw web gateway testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the need for a local testing environment to efficiently validate and debug changes made to the IronClaw web gateway using Docker containers and browser automation tools.

Core Features & Use Cases

  • Build & Test Images: Facilitates the creation of Docker images for IronClaw, specifically targeting local development and testing.
  • Containerized Environment: Runs IronClaw within Docker containers, allowing for isolated testing with customizable configurations.
  • Browser Automation: Utilizes Chrome MCP for automating browser interactions, such as verifying page elements and taking screenshots for debugging.
  • Use Case: When developing new features or fixing bugs in IronClaw, this skill can help developers quickly spin up a test environment, apply their changes, and perform automated testing before deployment.

Quick Start

Use the local-test skill to start a Docker container with the test IronClaw gateway, and access it in a browser at http://localhost:3003/?token=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 web gateway changes locally using Docker?

Test web gateway changes locally by spinning up Docker containers that automatically build and run your application, enabling fast iteration in an isolated environment. This containerized approach ensures your testing environment remains consistent and separate from your host setup.

How does browser automation work for local UI testing?

Browser automation for local UI testing works by utilizing Chrome to interact with your running web gateway, verifying page elements, and capturing screenshots for debugging. This automated interaction allows you to validate UI changes without manual clicking.

Do I need Docker to run local development testing for my web gateway?

Yes, Docker is required to run local development testing for your web gateway. The testing process relies on Docker containers to build the application images and provide the isolated environment needed to safely apply and validate code changes.

What is the best way to iterate on web gateway features in an isolated environment?

The best way to iterate on web gateway features in an isolated environment is using Docker containers to build and run the application. This approach allows you to quickly apply changes, spin up a test instance, and debug before deployment.

Can I use Chrome browser automation to verify page elements in a Docker test environment?

Yes, you can use Chrome browser automation to verify page elements in a Docker test environment. The testing setup supports automated browser interactions, allowing you to validate UI components and capture screenshots for debugging your web gateway.

What port and token do I need to access the local test gateway in a browser?

To access the local test gateway in a browser, you need port 3003 and the token 'test'. Simply navigate to http://localhost:3003/?token=test after starting your Docker container to view and interact with the running application.