Practical Interview Questions

Quiz: how to test a login form, what to do when time is short, retest and regression, API and Postman, test cases, test report and SQL.

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. You are asked: “How would you test a login form?” Which answer is the most complete?

    A strong answer lists both positive and negative scenarios and boundary values, and also mentions non-functional checks. This shows structured thinking.

  2. There is one day left before the release and much more to check than you can manage. Where do you start?

    When time is short, tests are prioritised by risk and business value. It is also important to tell the team what stays unchecked so that the release decision is made consciously.

  3. After a build, five fixed bugs are returned to the team, and there is little time to retest. Which bug do you check first?

    Retesting is prioritised too: first the bugs that the release and the main user scenarios depend on. The rest are checked as time allows, and the team is told what remains unchecked.

  4. How do you explain in simple words what an API is?

    An API is an interface for programs to communicate. The front end sends a request to the API, the server processes it and returns a response. A tester checks requests and responses directly, without the UI.

  5. You sent a request in Postman. What should you check in the response?

    The status code shows the result (200, 201, 400, 404, etc.), in the body you check the structure and data, in the headers, for example, the content type. Response time matters for performance.

  6. What does a test case usually include?

    A test case should let any tester repeat the check in the same way. Bugs found are recorded separately in bug reports, and the results of a run in a test report.

  7. What does a test report usually show after a test run?

    A report helps the team and the manager decide on a release: it shows, briefly and with facts, the state of quality and the remaining risks.

  8. An interviewer asks: “Why does a tester need SQL?” Which answer is the best?

    Not everything is visible through the UI: SQL lets you verify that a record was created, changed or deleted as it should be. Simple SELECT queries are usually enough.