Skip to main content

Module 1 · Understanding QA

What a QA engineer does

Responsibilities of the role, and the difference between assuring quality and testing a product.

About 8 min reading and 5 min practice (estimates)

Loading progress…

Read

Learning objectives

  • Describe the main responsibilities of a QA engineer.
  • Explain the difference between quality assurance (QA) and testing.
  • Recognise that quality is shared by the whole team, not handed to QA at the end.

Explanation

A QA engineer helps a team release software that does what people need, reliably and safely. Much of the job is finding information early: asking what a feature should do, spotting gaps in requirements, testing the product, and reporting clearly what works, what doesn't and what has not been checked.

QA and testing are related, not identical

  • Quality assurance is about the process: the habits and practices that make defects less likely — clear acceptance criteria, reviews, a definition of done, automated checks in the pipeline.
  • Testing is one activity within that: evaluating the product to find problems and gather evidence about how it behaves.
  • Testing can show that defects exist; it cannot prove that there are none. Good QA reports confidence and remaining risk honestly.

Typical responsibilities

  • Reviewing requirements and user stories for gaps and contradictions.
  • Planning what to test, based on risk.
  • Designing and running tests — scripted and exploratory.
  • Writing clear, reproducible bug reports and retesting fixes.
  • Building and maintaining automated checks where they pay off.
  • Summarising test results so the team can decide whether to release.

Example: gift wrapping at Dar Al Souq

Dar Al Souq, a fictional online shop used throughout this path, plans to add an optional gift-wrapping service. Quality work happens long before anyone clicks a button:

  1. In planning, QA asks: Can every product be wrapped? Is there a fee? Does wrapping change the delivery date? (Assurance — preventing misunderstandings.)
  2. During development, QA prepares test ideas and agrees which checks will be automated.
  3. When the feature is ready, QA tests it: adding wrapping, removing it, combining it with a promotion code, ordering in Arabic and English. (Testing.)
  4. Before release, QA summarises: what passed, two open low-risk issues, and one area not tested (wrapping for very large items).

Common mistakes

  • Treating QA as a gate at the very end, when changes are most expensive.
  • Measuring a tester only by the number of bugs found.
  • Saying a feature is "bug-free" instead of describing what was tested and what risk remains.
  • Testing only the happy path described in the ticket.

Try

Practise what you just read. Answers are checked here; nothing is graded publicly or counts toward Bug Arena.

Exercise

Which of these is a quality assurance activity rather than a testing activity?

Choose one answer.

Review

Check yourself — you should now be able to:

  • Describe the main responsibilities of a QA engineer.
  • Explain the difference between quality assurance (QA) and testing.
  • Recognise that quality is shared by the whole team, not handed to QA at the end.

Practise in QA Lab

References

Continue

When you’re ready, mark the lesson complete in the Try step and move on.

Marked as read when you reach the end of the lesson.