Interview preparation for testers in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of a software testing interview?

To assess your understanding of testing concepts, problem-solving skills, and how you approach finding and reporting bugs.

beginner

Name three common types of software testing you should know for an interview.

Functional testing, regression testing, and performance testing are common types you should be familiar with.

intermediate

Why is it important to understand the software development lifecycle (SDLC) in a testing interview?

Because testing fits into the SDLC, and knowing when and how to test helps you work better with developers and deliver quality software.

beginner

What is a test case and why should you be able to write one during an interview?

A test case is a set of steps to check if a feature works correctly. Writing one shows you can plan and organize your testing clearly.

intermediate

How can you prepare for behavioral questions in a tester interview?

Think of examples from your experience where you solved problems, worked in a team, or handled challenges. Practice explaining them clearly.

Which of the following is NOT a typical responsibility of a software tester?

A Writing test cases

B Reporting defects

C Fixing bugs in the code

D Performing regression testing

Fixing bugs is usually the developer's job, while testers focus on finding and reporting them.

What does regression testing ensure?

A Recent changes did not break existing functionality

B Old bugs are fixed

C Performance is improved

D New features work as expected

Regression testing checks that recent code changes do not cause new problems in existing features.

Which document describes the features to be tested and the testing approach?

A Bug Report

B Test Plan

C User Manual

D Release Notes

A Test Plan outlines what will be tested and how testing will be done.

During an interview, how should you handle a question you don’t know the answer to?

A Guess randomly

B Change the topic

C Stay silent

D Be honest and explain how you would find the answer

Honesty and showing problem-solving skills are valued more than guessing.

What is the purpose of writing clear bug reports?

A To help developers understand and fix issues quickly

B To confuse developers

C To delay the release

D To show off testing skills

Clear bug reports help developers reproduce and fix problems efficiently.

Explain how you would prepare for a software testing interview.

Think about both technical and soft skills preparation.

Describe the difference between functional and non-functional testing.

Focus on what each type tests and why it matters.

Practice

1. What is the main purpose of software testing in a project?

easy

A. To write code for new features

B. To find defects and ensure the software works as expected

C. To design the user interface

D. To manage the project timeline

Solution

1. Step 1: Understand the role of testing

   Testing is done to check if the software behaves correctly and to find any bugs.

2. Step 2: Compare options with testing goals

   Only To find defects and ensure the software works as expected talks about finding defects and verifying software behavior, which matches testing purpose.

3. Final Answer:

   To find defects and ensure the software works as expected -> Option B

4. Quick Check:

   Testing = Find defects + Verify behavior [OK]

Hint: Testing finds bugs and checks software works [OK]

Common Mistakes:

• Confusing testing with coding
• Thinking testing manages project tasks
• Mixing testing with design roles

2. Which of the following is the correct syntax to write a test case title?

easy

A. verify_user_login_with_valid_credentials

B. verify user login with valid credentials

C. VerifyUserLoginWithValidCredentials

D. "Verify user login with valid credentials"

Solution

1. Step 1: Identify proper test case title format

   Test case titles should be clear, descriptive, and readable, usually in sentence case with quotes.

2. Step 2: Evaluate options for clarity and format

   "Verify user login with valid credentials" uses clear sentence case with quotes, making it easy to understand. Others are less readable or informal.

3. Final Answer:

   "Verify user login with valid credentials" -> Option D

4. Quick Check:

   Clear descriptive title in quotes = "Verify user login with valid credentials" [OK]

Hint: Test case titles are clear sentences in quotes [OK]

Common Mistakes:

• Using camelCase or snake_case for titles
• Writing titles without quotes or punctuation
• Using all lowercase without clarity

3. Consider this test scenario: A login form accepts username and password. Which test case will fail if the password field allows empty input?

Test Case: Verify login with empty password
Steps:
1. Enter valid username
2. Leave password empty
3. Click login
Expected Result: Login should fail with error message

What will be the test execution result?

medium

A. Fail, because login succeeds with empty password

B. Pass, because empty password is allowed

C. Pass, because login fails as expected

D. Fail, because username is invalid

Solution

1. Step 1: Understand the test case and expected behavior

   The test expects login to fail when password is empty, showing an error.

2. Step 2: Analyze the actual behavior described

   The password field allows empty input, so login succeeds, which is against expected result.

3. Final Answer:

   Fail, because login succeeds with empty password -> Option A

4. Quick Check:

   Expected fail but login succeeds = Fail [OK]

Hint: If actual differs from expected, test fails [OK]

Common Mistakes:

• Assuming empty password is valid
• Confusing pass/fail with allowed inputs
• Ignoring expected error message

4. You wrote this test step: Click the submit button but the test fails because the button is not found. What is the most likely cause?

medium

A. The locator used to find the button is incorrect or outdated

B. The submit button does not exist in the application

C. The test script has syntax errors

D. The test environment is down

Solution

1. Step 1: Identify the failure reason for 'button not found'

   This usually means the test script cannot locate the button element on the page.

2. Step 2: Evaluate possible causes

   Incorrect or outdated locator is the most common cause, as UI changes can break locators.

3. Final Answer:

   The locator used to find the button is incorrect or outdated -> Option A

4. Quick Check:

   Button not found = Locator issue [OK]

Hint: Check locators first when element not found [OK]

Common Mistakes:

• Assuming button is missing without checking locator
• Blaming syntax errors without evidence
• Ignoring environment status

5. You have a list of test cases with their results:

[{"id":1, "result":"pass"}, {"id":2, "result":"fail"}, {"id":3, "result":"pass"}, {"id":4, "result":"fail"}]

How many test cases must be re-executed after fixing defects?

hard

A. 3

B. 4

C. 2

D. 1

Solution

1. Step 1: Identify test cases with failed results

   From the list, test cases with id 2 and 4 have result 'fail'.

2. Step 2: Determine re-execution count

   Only failed test cases need re-execution after defects are fixed, so count is 2.

3. Final Answer:

   2 -> Option C

4. Quick Check:

   Failed tests = 2 [OK]

Hint: Re-run only failed test cases after fixes [OK]

Common Mistakes:

• Counting all test cases instead of only failed
• Confusing pass with fail
• Ignoring test case results