Stop 01 · QA & Software Testing FoundationsTopics · 9/9

Key Tools Overview (Manual, Automation, API, Performance)

In short

QA job posts are full of tool names. Here's a quick map of what each family of tools does, so the names stop sounding random.

A preview of the toolkit this roadmap builds — manual test management tools, automation frameworks (Selenium, Playwright), API testing tools (Postman), and performance testing tools (JMeter).

The purple blob opens a big toolbox full of spanners, gauges and screwdrivers.

Think of it like this

A mechanic's toolbox

A mechanic doesn't use a spanner for everything. There's a jack to lift the car, a gauge for tyre pressure, a scanner for engine faults. QA tools are the same: each family does one kind of job well.

Watch it happen

The QA toolkit by job

QA toolkit

Manual

Automation

API

Performance

Jira, TestRail

Playwright

Postman

JMeter, k6

1/4Manual work: Jira tracks bugs and stories, tools like TestRail store test cases and results.

The big ideas

What you need to know

Management tools organise work

Bug trackers and test case tools keep a shared record of what was tested and what broke.

Browser automation repeats clicks

Automation tools run the same UI checks on every build, much faster than a human can.

API tools skip the UI

Testing the API directly is quicker and more stable than going through screens.

Load tools test under pressure

They answer 'what happens when 5,000 people log in at the same minute?'

See it in code

Walk through the code

1import { test, expect } from "@playwright/test";2 3test("example.com has the right title", async ({ page }) => {4  await page.goto("https://example.com");5  await expect(page).toHaveTitle(/Example Domain/);6});

1/3Import the test runner and the expect helper from Playwright.

A tiny Playwright test. It opens a real browser, loads the page and checks the title. You'll write many of these later.

Save yourself the pain

Common mistakes

Oops

Trying to learn every tool name on a job post at once.

Do this instead

Learn one tool per family well. The ideas carry over, and switching tools later is easy.

Oops

Thinking tools replace testing skill.

Do this instead

A tool only runs the checks you design. Good test ideas still come from you.

Your mission

Meet three tools

~30 min

Quick check

You want to check that the 'create order' endpoint returns 201 without opening the website. Which tool family fits?

Go deeper

1Skim the table of contents of each remaining phase to see how the tools fit together.
2Learn that most real QA engineers use several of these tools depending on the task.
3Set a rough personal priority order — most beginners should master manual testing first.