← QA Library
Chapter 17 / 19 · 7 min read

Everyday QA tools

The toolbox of a working tester: bug trackers, test management, DevTools, API clients, proxies, Git, CI and screen capture.

Tools don't replace thinking, but the right ones turn an hour of work into ten minutes. Here's what a modern tester uses day to day, and what each tool is best at.

The toolbox

TaskPopular tools
Bug tracking and tasksJira, YouTrack, Linear, GitHub Issues
Test managementTestRail, Qase, Zephyr, Xray, or checklists in a wiki
Browser investigationChrome / Firefox DevTools
API testingPostman, Insomnia, Bruno, curl
Traffic interceptionCharles, Proxyman, Fiddler, mitmproxy
MobileAndroid Studio and ADB, Xcode, TestFlight
Version controlGit, GitHub, GitLab, Bitbucket
CI/CDGitHub Actions, GitLab CI, Jenkins
Screenshots and videoBuilt-in OS tools, ShareX, Loom, OBS
Test dataFaker libraries, Mockaroo, temporary email services

DevTools: five tabs worth knowing

  • Elements: inspect and temporarily edit HTML and CSS — check how text behaves when it's longer
  • Console: JavaScript errors and warnings; always attach them to bug reports
  • Network: every request with status, timing, headers and body; throttle to slow 3G
  • Application: cookies, localStorage, cache; clear them to test as a new user
  • Device toolbar: emulate phone screen sizes and touch

Git for testers

You don't need to be a developer to use Git. It lets you read what changed in a release, check out a branch to test it locally, and keep automated tests next to the code.

git clone https://github.com/company/shop.git
git checkout feature/promo-codes      # switch to the branch to test
git log --oneline -10                  # what changed recently
git diff main...feature/promo-codes    # all changes in the feature
git pull                               # get the latest version

API clients

Postman or a similar tool lets you send requests without a UI: test validation that the front end hides, prepare data quickly and save collections of requests your team can reuse. Collections can run in CI with Newman.

Proxies

A proxy such as Charles or Proxyman sits between the app and the server and shows all traffic, including from mobile apps. You can also change responses on the fly — return an error, slow down a request, change a price — to test how the app handles situations that are hard to reproduce for real.

Capturing evidence

A short video with the console open is often the fastest way to explain a bug. Name files clearly, crop to what matters, and never include real customer data or passwords in screenshots.

Learn your tools deeply rather than collecting many. A tester who masters DevTools and an API client finds more bugs than one who knows twenty tools superficially.