nextura-qa-acceptance
QA acceptance testing and validation. Use when validating features against requirements.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install alicoding-nextura-nextura-qa-acceptance
Repository
Skill path: .claude/skills/nextura-qa-acceptance
QA acceptance testing and validation. Use when validating features against requirements.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: alicoding.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install nextura-qa-acceptance into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/alicoding/nextura before adding nextura-qa-acceptance to shared team environments
- Use nextura-qa-acceptance for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: nextura-qa-acceptance
scope: nextura
description: >
QA acceptance testing and validation.
Use when validating features against requirements.
version: 2.0.0
triggers:
- qa acceptance
- validate feature
- acceptance testing
- verify requirement
gates:
pre:
- "test -d tests/e2e"
post:
- "pytest tests/e2e/ -v"
---
# QA Acceptance
Validate features against requirements using acceptance criteria.
---
## Quick Start
1. Load requirement from SSOT
2. Extract acceptance criteria
3. Map to test cases
4. Execute and record results
---
## Requirement to Test Mapping
```yaml
# From REQ-XXX.yaml
acceptance_criteria:
- "User can login with valid credentials"
- "Invalid password shows error message"
- "Account locks after 5 failed attempts"
```
Each criterion = one test case.
---
## Test Structure
```
tests/e2e/
├── conftest.py
├── features/
│ └── login.feature # Gherkin specs
└── steps/
└── login_steps.py # Step implementations
```
---
## BDD Format
```gherkin
Feature: User Login
@REQ-LOGIN-001
Scenario: Successful login
Given a registered user
When they enter valid credentials
Then they see the dashboard
```
---
## STOP GATES
### STOP GATE 1: Requirement Exists
**Check:** Does requirement exist in SSOT?
**Pass:** REQ-XXX.yaml found
**Fail:** STOP. Create requirement first.
### STOP GATE 2: Criteria Defined
**Check:** Are acceptance criteria defined?
**Pass:** acceptance_criteria populated
**Fail:** STOP. Add acceptance criteria.
### STOP GATE 3: Tests Pass
**Check:** Do all acceptance tests pass?
**Pass:** pytest tests/e2e/ passes
**Fail:** STOP. Fix failures or update criteria.
---
## Quick Reference
```
TRACEABILITY
@REQ-XXX tag in tests
traces_to in requirements
COMMANDS
pytest tests/e2e/ -v
behave features/
```
---
## Reference Files
- [reference/bdd.md](reference/bdd.md) - BDD patterns
- [reference/traceability.md](reference/traceability.md) - Requirement linking