skills.rest
werlang
werlangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-first-delivery

Validates behavior changes in Express API and web services with Jest tests and browser checks.

Updated Feb 25, 2026
Search Tags:#testing#validation#jest#regression#docker-compose#express#test-driven-development
One-click install
npx skills add https://github.com/werlang/event-hub --skill test-first-delivery-werlang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-first-delivery
Source: https://github.com/werlang/event-hub/tree/main/.agents/skills/test-first-delivery
Command: npx skills add https://github.com/werlang/event-hub --skill test-first-delivery-werlang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Feature work and bug fixes in the Academic Events repository often ship without adequate test coverage or validation, leaving regressions undetected across the api/ and web/ services. This Skill enforces a test-first delivery contract so every behavior change is backed by updated automated tests or explicit manual validation. ## Core Features & Use Cases - Test-First Quality Contract: Requires API changes to update and run the committed Jest unit suite in api/tests/unit until 100% of tests pass, and web changes to update the committed web/tests suite. - Frontend Test Design Guidance: Helps choose the narrowest honest harness for web changes, including pure helper tests, jsdom plus VM workflow tests, and spawned Express route/template checks. - Manual Browser Validation: Provides a maintained route-by-route smoke checklist for /, /login, /week, and /dashboard when browser interaction cannot be automated. - Use Case: When adding a new event moderation endpoint to the Express API, use this Skill to write success and edge-case Jest tests, run the Compose test command, fix failures, and report exactly what was validated. ## Quick Start Ask the agent to implement a feature or fix in the api or web service and require it to follow the test-first delivery workflow with updated tests and a validation report.

Frequently Asked Questions about test-first-delivery

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

FAQPage Schema
How do I validate API changes in an Express repository with Jest?▼

Update or add Jest unit tests under api/tests/unit alongside the code change, then run docker compose -f compose.dev.yaml exec api npm run test:unit. The task is complete only when the suite finishes with 100% passing tests, covering both success and edge cases.

How do I test frontend changes without Playwright or Cypress?▼

Use the committed web/tests Node suite with pure helper tests, jsdom plus VM workflow tests, or spawned Express route checks. For browser-only interactions, follow the manual smoke checklist covering /, /login, /week, and /dashboard in a real browser session.

When should I bootstrap a new test harness instead of manual validation?▼

Bootstrap only when the harness stays small and local to the touched service, the behavior is deterministic, and it is less risky than manual checks. Prefer manual validation for cross-service flows, MySQL-dependent state, or CSS and focus-timing work.

What test harness should I use for web UI changes?▼

Match the narrowest honest harness: pure module assertions for deterministic helpers, jsdom plus VM tests for DOM mutations and page boot logic, and spawned web-server tests for SSR route output and template contracts. Avoid large snapshot-heavy tests.

What must be reported when finishing a behavior-changing task?▼

Report the tests or commands run, manual checks performed, and remaining gaps or unvalidated risk. Call out plainly when a real browser pass was not possible and note any setup such as seeded data or admin accounts used.

Related Skills

Explore More Software Engineering Skills→
FalkorDBFalkorDB
22

Use Docker Compose for repeatable local stacks

Define repeatable FalkorDB container environments with Docker Compose configuration files.

Official
Basic
himanshu231204himanshu231204
2

canary-watch

Monitor deployed web applications for regressions after production deploys.

Community
Intermediate
LazyNinja435LazyNinja435
1

Exploratory Testing

Perform structured exploratory testing sessions to identify software defects and usability issues.

Community
Intermediate
pnewsampnewsam
1

setup-browser-testing

Initialize or repair Playwright or Cypress browser-test infrastructure for Node projects.

Community
Advanced