qa-tester
Strict QA and test engineering skill for fullstack repositories. Use when writing test plans, implementing unit/integration/E2E tests, reproducing bugs, validating regressions, or preparing release readiness. Enforce deterministic tests, proper test pyramid, black-box verification, explicit execution approval, and zero fabricated results.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bayudsatriyo/qa-testerWhat This Skill Does
The qa-tester skill transforms the OpenClaw AI into a senior-level QA engineer and test strategist. It is designed to enforce rigorous, deterministic, and maintainable testing standards across fullstack repositories. By prioritizing a balanced test pyramid—70% unit, 20% integration, and 10% E2E—the skill ensures that the codebase remains robust and regression-proof without falling into the trap of over-relying on slow, brittle E2E tests.
Installation
Install the skill directly into your project via the ClawHub repository:
clawhub install openclaw/skills/skills/bayudsatriyo/qa-tester
Use Cases
- Test Strategy Development: Create comprehensive test plans for new features, identifying risks and choosing the correct test layers for optimal coverage.
- Bug Validation and Regression: Systematically reproduce bugs, identify the root cause, and implement permanent regression tests to ensure bugs stay fixed.
- Code Quality Improvement: Transitioning a repository from manual testing or disorganized ad-hoc scripts to a professional testing architecture.
- Release Readiness: Conducting final validations of critical user flows to ensure deployments are safe and feature-complete.
Example Prompts
- "I am implementing a new user onboarding flow. Can you outline a test strategy that covers unit tests for the validator and an E2E flow for the final submission?"
- "We have a bug where the discount code is not applying correctly in the checkout. Please help me reproduce this, identify the cause, and write an integration test to prevent it."
- "Review my current test suite. Do we have too many E2E tests? Propose a plan to move some coverage to the integration or unit layers."
Tips & Limitations
- Determinism First: The skill prefers deterministic outcomes. Avoid using arbitrary time-based delays; instead, wait for state changes or specific API conditions.
- Isolation: Always maintain test isolation. The skill enforces the use of fixtures or factories rather than shared database states.
- Explicit Approval: The skill is designed to prevent accidental execution. It will suggest commands for you to run rather than running them automatically, ensuring you maintain control over your production environment.
- Limitations: The skill does not automate physical hardware testing. It focuses on software contracts, API behavior, and UI/logic verification within the scope of the local repository.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bayudsatriyo-qa-tester": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution