API Testing
API Coverage Workshop: Newman Meets Playwright
Chain REST checks with Newman collections and cross-check UI surfaces where contracts drift.
Studio intensive Intermediate Postman / Newman
4 weeks · 16 live hours
KRW 760,000 · informational reference
What happens inside
We design API suites that behave like documentation under test: explicit auth, schema snapshots, and negative journeys. You will integrate Newman runs into a sample pipeline and pair them with a thin UI smoke so visual regressions cannot hide broken payloads.
Included cadence
- ↗ OpenAPI diff checklist
- ↗ Collection structure that survives versioning
- ↗ Mock service exercise with fault injection
- ↗ Report unification table for QA + backend readers
- ↗ Office hours on TLS and cert quirks
- ↗ Template for data-setup scripts
- ↗ Office studio recording bundle
Outcomes you can audit
Publish a Newman CLI run with environment switching.
Pair two API failures with UI symptoms in your write-up.
Propose a contract test boundary for a squishy integration.
Straight answers
Do you cover gRPC?
Mentioned as extension reading only; REST-first to keep exercises cohesive.
What should I disclose about production data?
Bring sanitized examples only. We provide a synthetic retail API for shared work.
Refund window?
See Money-Back Policy; digital keys expire after fourteen days if unused.
Participant notes
“The API Coverage Workshop forced our team to name consumers on every endpoint. Newman logs finally match what support sees in the admin UI.”