senior-qa-ui-e2e-testing

Orchestrate unit, integration, and end-to-end tests in JS/TS/Python.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BearyDevs/dotfiles --skill senior-qa-ui-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-qa-ui-e2e-testing
Source: https://github.com/BearyDevs/dotfiles/tree/main/.config/opencode/skills/senior-qa-ui-e2e-testing
Command: npx skills add https://github.com/BearyDevs/dotfiles --skill senior-qa-ui-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activates Monday — a senior QA engineer persona — to design, author, run, and diagnose tests across unit, integration, and end-to-end layers in JavaScript, TypeScript, and Python projects. It helps teams ensure test quality, rapid feedback, and consistent QA practices across features.

Core Features & Use Cases

  • Plan and write deep tests that exercise critical paths across unit, integration, and E2E layers.
  • Run deterministic test plans with vault-context awareness, test plans, and artifact preservation.
  • Reproduce, diagnose, and report test outcomes, including flaky-test handling and coverage improvements.

Quick Start

Use the skill to map a QA task end-to-end from planning to execution; then let Monday generate and run the tests and surface the results.

Frequently Asked Questions about senior-qa-ui-e2e-testing

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

FAQPage Schema
How do I plan and write end-to-end tests across unit and integration layers?

End-to-end test planning and authoring across unit, integration, and E2E layers is orchestrated through a senior QA persona that designs deep tests exercising critical paths in JavaScript, TypeScript, and Python projects. It generates structured test plans and surfaces artifacts for stakeholder approval.

What is the best way to fix flaky tests and improve test coverage?

Fixing flaky tests and improving coverage involves reproducing, diagnosing, and reporting test outcomes with deterministic test execution. The workflow enforces vault context awareness and artifact preservation to isolate non-deterministic behavior and validate critical paths.

Can I run smoke tests and QA features before delivery in Python and TypeScript?

Smoke tests and pre-delivery QA are supported natively for JavaScript, TypeScript, and Python projects. The workflow activates phase-driven planning to map tasks end-to-end, execute test suites, and surface results for stakeholder approval.

Does this approach enforce deterministic test execution and project conventions?

Deterministic test execution and project conventions are enforced during test suite execution by applying vault context awareness and phase-driven planning. This ensures tests run consistently and artifacts are preserved across unit, integration, and end-to-end scopes.

Why do my end-to-end tests fail to maintain consistent results across runs?

End-to-end tests fail to maintain consistency when deterministic test execution and vault context awareness are not applied. The workflow enforces project conventions, artifact preservation, and phase-driven planning to diagnose flaky tests and ensure rapid feedback.

How do I generate and run a full test plan from planning to execution?

Generating and running a full test plan requires mapping a QA task end-to-end from planning to execution. The workflow designs, authors, and runs tests across unit, integration, and E2E layers, then surfaces the results and artifacts for diagnosis.