quality-engineer

Implement and execute automated tests across frontend, backend, and AI layers.

6|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/gajakannan/nebula-crm --skill quality-engineer-gajakannan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-engineer
Source: https://github.com/gajakannan/nebula-crm/tree/main/agents/quality-engineer
Command: npx skills add https://github.com/gajakannan/nebula-crm --skill quality-engineer-gajakannan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Quality teams often struggle with fragmented testing across frontend, backend, and AI layers, resulting in slow feedback and higher production risk. This Skill provides a unified approach to plan, implement, and maintain automated tests, infrastructure, and governance across the Nebula CRM solution.

Core Features & Use Cases

  • Test Pyramid guidance and cross-stack strategy for full-stack projects.
  • Automated frontend/backend/AI tests using Playwright, xUnit, pytest, and related tooling.
  • CI/CD integration with coverage enforcement, security and accessibility checks, and reporting.

Quick Start

Install and configure the test environment described in planning-mds (Testcontainers, MSW, Playwright). Start by drafting the test plan from acceptance criteria, then implement unit/integration/E2E tests and wire into CI. Run tests locally and generate coverage reports to verify thresholds.

Frequently Asked Questions about quality-engineer

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

FAQPage Schema
How do I automate end-to-end testing across frontend, backend, and AI layers?

To automate end-to-end testing across frontend, backend, and AI layers, implement a unified test strategy using Playwright, xUnit, and pytest. This enforces the test pyramid and integrates security, accessibility, and performance checks throughout your CI/CD pipeline.

What is the best way to enforce test coverage and the test pyramid in a full-stack project?

Enforcing test coverage and the test pyramid in a full-stack project requires drafting a test plan from acceptance criteria, then implementing unit, integration, and E2E tests. This approach achieves ≥80% coverage for business logic and wires automated reporting into CI.

How do I integrate Testcontainers and Playwright into a CI/CD pipeline for test automation?

To integrate Testcontainers and Playwright into CI/CD for test automation, configure the test environment described in your planning documents, execute tests locally to generate coverage reports, and wire the test runs into your CI pipeline to verify coverage thresholds.

Can I use Playwright and pytest for security, accessibility, and performance checks?

Yes, you can use Playwright and pytest alongside common tooling like Bruno CLI and Trivy to execute security, accessibility, and performance checks. This integration ensures comprehensive quality assurance across multi-stack architectures during feature development.

Does this test automation approach work for AI layer testing in multi-stack architectures?

Yes, this test automation approach works for AI layer testing in multi-stack architectures by applying a cross-stack strategy. It plans, implements, and maintains automated tests and infrastructure specifically designed to validate AI layers alongside frontend and backend components.

Why do I need Testcontainers and MSW for full-stack quality assurance?

You need Testcontainers and MSW for full-stack quality assurance to properly configure the test environment and isolate dependencies. Setting up this infrastructure resolves fragmented testing issues, providing faster feedback and reducing production risk across your application.