Early access The free plan is live — unlimited tests, no card, yours to keep Get started →
Resources

Software testing communities

Forums, newsletters and podcasts worth the subscription, and the one place to ask a question nobody at work can answer.

8 resourcesKeep going

Testing is a field where most of the useful knowledge is unpublished, sitting with people who have made the mistake you are about to make. Nobody writes a blog post called “we spent four months on a suite nobody ran”. They will tell you about it in a forum thread.

The other reason to be somewhere is that testing is frequently a team of one. A developer disagreeing with your bug report, a manager asking why the automation did not catch it, a decision about whether to quarantine or delete — those are much easier with somebody outside the building to check your reasoning against.

How to get a useful answer

Post what you actually tried, what happened, and what you expected instead — in that order. Most unanswered questions are unanswerable: they describe a proposed fix rather than the problem, so the only people who could help cannot tell what is wrong. And say which tool and version, because half of the plausible answers depend on it.

Places to ask

4 entries
  1. The forum attached to the largest testing community there is, and one of the few places where a vague question about how to approach something gets a considered answer rather than a link. Reading it is free; posting needs an account.

    club.ministryoftesting.com
  2. Unfiltered questions from working testers, including the career ones nobody asks at work: what to charge, when to leave, whether the certification is worth it.

    www.reddit.com
  3. Not a forum, and listed anyway: an unusually high proportion of Playwright questions are already answered in a closed issue, often by a maintainer, often with the reasoning. Search it before asking anywhere else. The Discord link on Playwright's community page is where the open-ended questions go.

    github.com
  4. The Q&A site for testing practice rather than code. Slower than Reddit, better archived, and the accepted answers tend to be considered.

    sqa.stackexchange.com

Things that arrive on their own

3 entries
  1. One email a week with the best testing articles, jobs and tools of that week. Consistently good signal and no filler, which is not the norm for newsletters in this space.

    softwaretestingweekly.com
  2. Interviews with automation practitioners, several times a week. Good for the commute, and a reliable way to hear about a tool before it reaches your team.

    testguild.com
  3. Longer-form written pieces from working practitioners, edited properly rather than published raw. The counterweight to a diet of blog posts and release notes, and the place where the awkward questions about the profession get argued out at length.

    www.ministryoftesting.com

Ours

1 entry
  1. Read without an account, post with a free one. Questions, issues and discussion about testing generally, not only about the product. Cross-tenant on purpose: the whole value is that somebody outside your organisation answers.

    qaright.com
Missing something? If there is a resource you send to every new tester on your team, tell us and we will read it. The list stays short on purpose; each entry has to earn its place, and entries that stop earning it get removed rather than left to rot.

Reading is the slow way to learn how a suite behaves. Record one against your own app, free, and watch what the report says.

Get started free See how it works