Custom track
Automation Quality Track
This page distills how WiseUp APIWise QA Academy sequences browser automation, API contract drills, and reporting flow so evening learners can see the whole prism at once—not as isolated homework blocks.
Test pyramid, rendered honestly
We teach the pyramid as a risk conversation: wide bases of fast checks, narrow peaks of expensive UI journeys, and explicit gaps where manual exploration still earns its keep.
- • Unit-adjacent checks stay close to developers—QA supplies fixtures, not ownership battles.
- • Integration lanes document cross-org workflow assumptions with receipts.
- • UI peaks carry trace bundles and naming discipline so triage stays civil.
Framework setup rituals
Setup week is deliberately boring: pinned tool versions, shared secrets handling, and a CI graph screenshot pasted into the cohort wiki. We refuse “it worked on my laptop” as a status.
- 1. Freeze toolchain manifests with mentor countersign.
- 2. Wire smoke lane to post artifacts even when green.
- 3. Publish rollback + feature-flag note alongside first merge.
Reporting flow
Reporting is treated as product work: dashboards show decisions, not vanity counts. Each cohort ends with a one-page “decisions log” suitable for internal portals.
Activity logs stay tied to incident IDs; narrative summaries land in the portfolio pack mentors review with you.
