Your bootcamp. Your pace.
No cohorts, no sign-ups, no lectures. Here is exactly how to get the most out of it.
The two-minute overview
Four steps. That is the whole model.
Find your level
Not sure where you sit? The roadmap asks three quick questions and points you at the right place. No test, no sign-up.
Go to the roadmap →Read & learn
Start at your level’s intro page, then work through the technique pages in order. Each one is short. Read it, understand it, move on.
Start at Grad intro →Practice
Each level has practice pages with planted bugs. Work in blind mode first — find everything you can, then check the answer key.
Try a practice page →Apply & return
Use the technique library as a reference on real projects. When you hit something unfamiliar, come back and look it up.
Browse the library →How the levels connect
You do not need to finish one track before touching the other.
Manual QA Foundation
Grad → Junior → Senior → Test Lead. Each level builds on the last. You start by catching obvious defects (typos, broken links) and work up to security gaps, race conditions, and accessibility failures.
This track builds what most people call the tester’s eye — the intuition for where things go wrong. You do not need to write a single line of code.
- Grad — obvious defects, first bug reports
- Junior — form validation, boundary values
- Senior — accessibility, browser quirks, state bugs
- Test Lead — security, race conditions, data integrity
Quality Engineering (Automation)
Junior SDET → Mid-Level → Senior QE → Automation Lead → Architect. This track covers code-driven testing — Playwright, Page Object Models, API testing, CI pipelines, synthetic data, and eventually Agentic AI mesh architectures.
If you have a development background, you can start here directly. If not, completing Manual Grad and Junior first gives you the testing intuition that makes the automation work meaningful.
- Junior SDET — robust locators, first assertions
- Mid-Level — Page Objects, API testing, CI
- Senior QE — synthetic data, telemetry, framework design
- Automation Lead — ROI reporting, tool selection, team mentoring
- Architect — Infrastructure as Code, chaos, Agentic AI
The most common path: Start at Manual Grad, work through to Junior, build the tester’s eye, then jump into Automation Junior SDET. Many learners find that doing even just 2–3 weeks of manual testing first makes the automation make much more sense — you are writing tests for bugs you have already learned to spot.
How long will it take?
These are honest estimates for someone starting from scratch at each level. Your own pace will vary.
| Level | Suggested pace | Weeks to complete | Total hours |
|---|---|---|---|
| Grad | 2–3 hrs / week | 4–6 weeks | 10–15 hrs |
| Junior | 3–4 hrs / week | 6–10 weeks | 20–30 hrs |
| Senior | 4–5 hrs / week | 8–12 weeks | 30–50 hrs |
| Test Lead | 5+ hrs / week | 10–16 weeks | 50–80 hrs |
| Automation (per level) | 4–5 hrs / week | 6–10 weeks | 25–40 hrs |
These figures assume zero prior experience at that level. If you are already working in QA, you will move significantly faster — many experienced testers use the Senior or Test Lead content as a gap-filler rather than end-to-end study. There is no timer and no pressure. Close the tab, come back next week, and your progress is still there.
Using the technique library
The library is not a linear path — it is a reference. Dip in, dip out. Two ways to use it:
Top-down
Start from a technique page, understand it fully, then find the practice page where it applies. Good if you are working through a level systematically.
- Pick a technique (e.g. boundary value analysis)
- Read the hook, the rule, the analogy, and the worked examples
- Open the linked practice page and apply it immediately
- Check your findings against the answer key
Bottom-up
Hit a bug on a practice page that you cannot explain, or encounter something on a real project you do not have a name for. Look it up in the library.
- Notice something odd on a practice page or real site
- Search or browse the library by category
- Read until you understand what you were looking at
- Return to the practice page with fresh eyes
Every technique page follows the same structure: a hook, a plain-English rule, an analogy, a worked NZ example, a decision guide, industry reality, interview questions, and nine self-checks. Once you know the format, you can scan any page quickly and find what you need.
The Testing Pyramid
Few · Slow · High value
Medium · Moderate · Service boundaries
Many · Fast · Cheap · Pure logic
The pyramid shape reflects the ideal ratio — not a strict rule. Invert it and your CI pipeline collapses.
Building a portfolio as you go
You are doing real work on these practice pages. Treat it like that.
-
Screenshot your bug finds. When you find a defect on a practice page, take a screenshot that shows the defect title, steps to reproduce, and expected vs. actual result. Do not just note the answer key answer — write it up as if you were reporting it to a developer.
-
Use the bug report template. The Bug Report template gives you the standard format NZ employers recognise. Fill one out per defect find. It takes three minutes and gives you a document you can show in an interview.
-
Save them somewhere. A Google Doc or Notion page works well. After 5–10 solid defect reports, you have the basis of a portfolio. Date each one so you can show progress over time.
-
Link technique to defect. In your portfolio doc, tag each defect report with the technique that uncovered it (e.g. “found via boundary value analysis on the KiwiSaver contribution field”). This is exactly the kind of answer that lands well in interviews.
-
After 10 reports, you are ready to talk about it. You now have real examples of defect reporting, test analysis, and technique application. That is more than most candidates bring to a first QA interview.
Combining with ISTQB
The bootcamp is not an exam crammer. But the material lines up well.
Grad + Junior
Covers the core CTFL syllabus in a practical way — test design techniques, defect reporting, SDLC basics, and test documentation. Use the ISTQB guide pages linked from the Grad and Junior sidebars to map bootcamp content to exam objectives.
Senior + Test Lead
Senior level covers risk-based testing, accessibility, and state testing relevant to CTAL-TA. Test Lead covers strategy, governance, and metrics that map directly to CTAL-TM. Both sidebars link to study mapping guides.
Automation track (all levels)
The full automation track covers framework design, CI integration, and quality gates that align with CT-TAS. Junior SDET through Architect progressively builds the technical depth the exam expects.
AI Testing track
The AI testing module covers CT-GenAI and CT-AI objectives alongside ISO/IEC TS 42119-2:2025. Metamorphic testing, neural network coverage, and hallucination detection are all covered with live hands-on labs.
The bootcamp cares whether you can actually test software, not whether you can recite definitions. The exam cares about both. Use the bootcamp for understanding and practice, and supplement with official ISTQB study material for the terminology and question formats.
NZ-specific advice
NZ employers tend to value practical over theoretical. A candidate who can show three well-written defect reports from a real practice page — with clear steps, expected vs. actual, and a severity call — is more interesting than one who can recite ISTQB definitions without having filed a bug in their life.
The interview banks at each level (/*/interview-prep/) have model answers written for NZ market expectations — typical interview formats, the kinds of follow-up questions NZ hiring managers use, and salary-relevant framing. When you are asked for a worked example in an interview, reach for the NZ-specific scenarios from the bootcamp: IRD tax calculation edge cases, ACC claim submission flows, NZTA licence validation, KiwiSaver contribution boundaries, or RealMe identity verification paths. These show local awareness, which matters for roles at government agencies, banks, and large NZ tech organisations.
Popular starting points
Not sure where to click first? Here are the four most reached-for pages.
The absolute starting point. What testing is, the vocabulary you need, and how to write your first bug report. Takes about 20 minutes to read.
Most popular technique Boundary Value AnalysisThe single most useful technique for form testing. Understand exactly where to look for validation failures — and why the edges are where the bugs hide.
Most practical for NZ roles Risk-Based TestingHow to decide what to test when you cannot test everything. Essential for any tester working in a team with time pressure — which is every team in NZ.
Most requested specialised Accessibility TestingWCAG 2.2 accessibility testing for web applications. Increasingly required by NZ government and public-facing projects. Covers screen readers, keyboard nav, and contrast.
Still not sure where to begin?
The roadmap will sort you out in two minutes.