Introducing the QualityMax QA Wiki

All posts

A team adds more automated tests. The suite turns green. The next release still raises questions: which risks did those tests cover, what did they actually assert, and where does the team need to investigate further?

Those questions shape testing decisions every day. Answering them takes a shared understanding of quality assurance, supported by sources the team can inspect.

The QualityMax QA Wiki is now public. It gives QA engineers, developers, and engineering leaders a place to explore testing practices and follow the sources behind an article. You can read it without creating a QualityMax account.

Start with the assumptions behind your test strategy

One article already live is What Testing Is NOT: Common Misconceptions in QA and Test Automation. It examines expectations around automation, coverage, and exploratory testing.

The article offers a useful starting point for a team discussion:

• Give automation and exploration clear roles. Repeatable checks and investigation contribute different kinds of information.
• Choose coverage around meaningful risks. A growing test count needs a connection to what matters for the product.
• Give exploratory sessions a purpose. Goals, context, and a charter help direct the work.

Read the full article and its linked sources, then bring one assumption to your next planning session. Ask how it affects the tests you choose, the time you spend maintaining them, or the evidence you use to make a release decision.

A public reference you can return to

The wiki collects QA knowledge in individual articles you can link directly from a test plan, pull request, onboarding document, or team conversation. Each published page has a stable address, so colleagues can read the same material and discuss a specific section.

Source links make that discussion easier to check. Follow them to the original material, consider its context, and decide how the guidance applies to your own product. The wiki gives the team a starting point for investigation; your application and its risks still determine the testing work.

Review is part of publishing

QualityMax staff review and approve the exact article revision before it becomes public. Research and drafts stay private, and editing an approved revision requires another review.

The review policy explains how articles use public sources and how to request a correction. If a section is wrong or a source has become outdated, send the article URL, the section, and a supporting public source. Corrections go through review before replacing the published article.

Use it with your team

For onboarding, pair a wiki article with an example from your own test suite. For planning, use it to make the team’s assumptions explicit. For a release discussion, ask which claims your current checks support and what still needs investigation.

We build test automation at QualityMax, and we want the reasoning behind testing to be as accessible as the tools. The public wiki is a place to develop that understanding together, with sources you can follow and a path to correct the material.