qa-engineer

What This Skill Does

The qa-engineer skill transforms your OpenClaw agent into a high-level software quality assurance expert. Designed for developers and engineers, this skill provides end-to-end guidance on creating robust test suites, implementing industry-standard testing strategies, and automating verification processes. It covers everything from unit-level verification in modern frameworks like Vitest and Jest to critical end-to-end user flows using Playwright or Cypress. Whether you are struggling with a flaky build, trying to increase branch coverage, or designing a test architecture from scratch, this skill offers actionable advice, code snippets, and structural improvements based on the Testing Pyramid and Testing Trophy philosophies.

Installation

You can install this skill directly via the command line within your OpenClaw environment: clawhub install openclaw/skills/skills/anton-abyzov/sw-qa-engineer

Use Cases

• Refactoring Legacy Code: Use this skill to write comprehensive regression tests before touching fragile legacy logic, ensuring you don't introduce breaking changes.
• Optimizing Test Suites: Get advice on converting slow, bloated integration tests into fast, isolated unit tests using proper mocking strategies with MSW.
• Implementing TDD: Follow the Red-Green-Refactor cycle under the guidance of the agent to build new features that are inherently testable and clean.
• Setting Up CI/CD Pipelines: Get recommendations for integrating tools like Lighthouse CI, Percy, or Snyk into your automated deployment pipelines to ensure quality before shipping.
• Improving Coverage: Identify gaps in your codebase by performing branch and statement analysis, using the agent to suggest edge cases you might have overlooked.

Example Prompts

1. "I am seeing flaky tests in my React app using Playwright. Can you review this test file and help me implement better waiting strategies and selector best practices?"
2. "I need to implement a testing strategy for a new Node.js microservice. Should I use the Testing Trophy approach? Please help me outline the unit, integration, and E2E test plan."
3. "Write a set of unit tests for this utility function using Vitest, ensuring we cover boundary values and throw errors for invalid input types."

Tips & Limitations

• Context is Key: For the most accurate code generation, always provide the agent with your existing test framework configuration and project structure.
• Focus on the Pyramid: Prioritize unit tests for business logic. While the agent can help with E2E, don't rely solely on them, as they are slow and expensive to maintain.
• Security Limitations: While the agent can suggest security practices like using Snyk or Bandit, it is not a substitute for a full-scale automated security audit or penetration testing. Always verify security patches in a staging environment.