QA Basics and the Tester’s Role

Quiz: testing vs QA, test levels, smoke and regression, positive and negative checks, incomplete requirements.

Question 1 of 8Correct: 0Incorrect: 0

Questions and explanations

Find an explanation for each question here. To test yourself, take the quiz above first.

  1. An interviewer asks: “What is the difference between testing and QA?” Which answer is the most accurate?

    Testing is a part of QA. QA also includes working with requirements, processes, reviews and defect prevention. A good answer shows you see the difference between “finding a bug” and “not letting it appear”.

  2. You are asked about test levels. What is checked at the integration testing level?

    Component (unit) testing checks a single part, integration testing checks the connections between parts, system testing checks the whole system, and acceptance testing checks readiness from the customer’s or business’s point of view.

  3. What is the difference between smoke testing and regression testing?

    Smoke answers “is it worth testing this build at all”. Regression answers “did anything that worked before stop working”.

  4. You are testing the “Age” field in a registration form (18–99 is allowed). Which check is negative testing?

    Positive testing checks that the system works with valid data. Negative testing checks that it reacts correctly to invalid data and actions.

  5. Which check is non-functional testing?

    Functional testing answers “what does the system do”, non-functional testing answers “how does it do it”: speed, security, usability, reliability.

  6. Why should a tester join the project at the requirements stage rather than after development?

    The earlier a defect is found, the cheaper it is to fix. A mistake in the requirements noticed before development never turns into a bug in the code.

  7. You get a task, but the requirements are incomplete: it is unclear what should happen when a field is empty. What do you do?

    A tester should not guess. A clarification immediately removes the risk that the developer and the QA understood the requirement differently, and the agreement stays in the documentation.

  8. What is acceptance testing?

    Acceptance testing is the last level: the customer or the business decides whether to accept the product. The other levels exist so that by this point no serious problems remain.