Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-test-setup
saas-test-setup
UnverifiedScaffold unit, integration, and E2E test runners plus GitHub Actions CI workflows.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| references/1-detect.md | markdown | 1.7 KB |
| references/2-plan.md | markdown | 1.3 KB |
| references/3-directories.md | markdown | 2.5 KB |
| references/4-ci.md | markdown | 3.5 KB |
| references/5-smoke-seed.md | markdown | 1.4 KB |
| references/6-summary.md | markdown | 1.7 KB |
references/6-summary.md
View on GitHub# /saas-test-setup — Phase 6: Post-Setup Summary
> Part of `/saas-test-setup`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.
## Phase 6: Post-Setup Summary
After writing all files, report:
```
Test infrastructure created for [engine].
Files created:
- tests/README.md
- tests/unit/ and tests/integration/ (Next.js / Vitest / Jest)
- tests/e2e/ (Playwright) or tests/unit/ (FastAPI / pytest)
- tests/smoke/critical-paths.md
- production/qa/evidence/.gitkeep
[stack-specific files]
- .github/workflows/tests.yml
Next steps:
1. Install test dependencies if not already present (`npm install -D vitest` or `poetry add --group dev pytest`)
2. Write your first test in the project's test root:
`tests/unit/[module]/[module]_[feature].test.ts` (Next.js), or
`tests/unit/test_[module].py` (FastAPI)
3. Run `/saas-qa-plan sprint` before your first sprint to classify stories and set
test evidence requirements. At `workflow: minimal` — the default — skip
this: there are no sprints. At `qa.level: minimal`, also the default, tests
are waived, so `/saas-dev-story` writes none. Raise `qa.level` with `/saas-settings`
to have it write them
4. `/saas-smoke-check` before every QA hand-off
Gate note: /saas-gate-check Technical Setup → Pre-Production now requires:
- the test root: tests/unit/ and tests/integration/ (Next.js / TypeScript), or
tests/unit/ (FastAPI / Python)
- .github/workflows/tests.yml
- At least one example test file
Run /saas-test-setup and write one example test before advancing.
(At `workflow: minimal` that gate requires only the engine.)
Verdict: **COMPLETE** — test framework scaffolded and CI/CD wired up.
```
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |