Skip to the content ForoHackers
Log inJoin

Quality assurance: start here

Quality assurance
#707 · Ophuscado · · Report

Quality assurance is the whole practice of making sure a product is good enough to ship and stays that way. Testing is one part of it. The rest is prevention: clear requirements, reviews, sound processes and measures that show where defects come from, so that fewer of them are made in the first place.

Key concepts

  • Prevention over detection: reviews, standards and early checks cost less than late fixes.
  • Test strategy and plan: what to test, how deeply, by whom, and when it is good enough to release.
  • Defect management: report, reproduce, prioritise, fix, verify and learn from each defect.
  • Exploratory testing: a skilled person investigates freely, learning and testing at the same time.
  • Release criteria and metrics: agreed conditions for shipping, and numbers that mean something.

Vocabulary

  • Verification and validation: building the product right, and building the right product.
  • Bug report: a description with steps to reproduce, expected and actual results.
  • Severity and priority: how bad a defect is, and how soon it must be fixed.
  • Root cause analysis: tracing a defect back to the process failure that let it through.

What to study, in order

  1. Learn the difference between verification, validation, testing and quality assurance.
  2. Write a clear bug report that someone else can reproduce in a minute.
  3. Draw up a test plan for a small application, with risks and priorities.
  4. Run an exploratory session with a time limit and notes of what you found.
  5. Take a real defect and do a root cause analysis, ending with a change to the process.

Related tags

#testing #requirements #code-review #ci-cd

Log in or join to reply.