Test case writing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a test case in software testing?

A test case is a set of instructions or steps designed to check if a software feature works as expected. It includes inputs, actions, and expected results.

beginner

Name three essential parts of a test case.

1. Test steps (actions to perform)
2. Test data (inputs used)
3. Expected result (what should happen)

beginner

Why is it important to write clear and simple test cases?

Clear and simple test cases help anyone understand and run the test easily, reducing mistakes and saving time during testing.

beginner

What does it mean if a test case 'passes'?

A test case passes when the actual result matches the expected result exactly, showing the feature works correctly.

beginner

Give an example of a good test case title.

Example: 'Login with valid username and password should succeed'. It clearly states what is tested and the expected outcome.

Which part of a test case describes what you expect to happen?

A Expected result

B Test data

C Test steps

D Test environment

The expected result tells what should happen if the test runs correctly.

Why should test cases be easy to understand?

A To avoid confusion and errors during testing

B To make testing longer

C So only developers can run them

D To hide bugs

Easy-to-understand test cases reduce mistakes and make testing faster and more reliable.

What is NOT usually part of a test case?

A Test data

B Expected result

C Code implementation details

D Test steps

Test cases focus on testing actions and results, not on how the code is written.

If a test case fails, what does it mean?

A The software works perfectly

B The actual result did not match the expected result

C The test case was written incorrectly

D The test environment is always wrong

A failure means the software did not behave as expected in that test.

Which title is a good test case title?

A Test 1

B Bug fix

C Check login

D Login with valid username and password should succeed

A good title clearly describes what is tested and the expected outcome.

Describe the key parts of a test case and why each is important.

Think about what you need to do, what you use, and what you expect.

Explain what it means when a test case passes or fails.

Focus on comparing what happens to what should happen.

Practice

1. What is the main purpose of writing test cases in software testing?

easy

A. To write the program code

B. To describe step-by-step how to test a feature

C. To design the user interface

D. To create marketing materials

Solution

1. Step 1: Understand the role of test cases

   Test cases provide clear instructions on how to test a specific feature or function.

2. Step 2: Differentiate from other activities

   Writing code, designing UI, or marketing are not related to test case writing.

3. Final Answer:

   To describe step-by-step how to test a feature -> Option B

4. Quick Check:

   Test case purpose = step-by-step test guide [OK]

Hint: Test cases guide testing steps clearly [OK]

Common Mistakes:

• Confusing test cases with coding tasks
• Thinking test cases design UI
• Mixing test cases with marketing

2. Which of the following is the correct format for a test case title?

easy

A. Test login with valid username and password

B. Check if login works

C. LoginTest123

D. TestCase1

Solution

1. Step 1: Identify clear and descriptive titles

   A good test case title clearly describes what is being tested, like Test login with valid username and password.

2. Step 2: Evaluate other options

   Options A, B, and C are vague or not descriptive enough for easy understanding.

3. Final Answer:

   Test login with valid username and password -> Option A

4. Quick Check:

   Clear descriptive title = Test login with valid username and password [OK]

Hint: Use clear, descriptive titles for test cases [OK]

Common Mistakes:

• Using vague or generic titles
• Using codes or numbers only
• Not describing the test purpose

3. Given this test case step: Enter username 'user1' and password 'pass123', what is the expected result?

medium

A. Page reloads without change

B. Error message appears

C. User is logged in successfully

D. Username and password fields clear

Solution

1. Step 1: Understand the test step

   The step inputs valid credentials, so the expected result is successful login.

2. Step 2: Analyze other options

   Error message or no change would mean failure, which is not expected here.

3. Final Answer:

   User is logged in successfully -> Option C

4. Quick Check:

   Valid login inputs = successful login [OK]

Hint: Valid inputs usually lead to success expected result [OK]

Common Mistakes:

• Assuming error message for valid inputs
• Confusing page reload with success
• Ignoring expected behavior for valid data

4. Identify the error in this test case step: Click the 'Submit' button without entering any data with expected result: Form submits successfully.

medium

A. Expected result should be an error message, not success

B. Step should include entering data before submit

C. Button name is incorrect

D. No error, test case is correct

Solution

1. Step 1: Analyze the test step

   Clicking submit without data usually triggers validation errors, not success.

2. Step 2: Check expected result correctness

   Expected result should be an error message indicating missing data.

3. Final Answer:

   Expected result should be an error message, not success -> Option A

4. Quick Check:

   Empty submit triggers error, not success [OK]

Hint: Empty form submit expects error, not success [OK]

Common Mistakes:

• Expecting success without input
• Ignoring validation rules
• Assuming button name error

5. You need to write a test case for a password reset feature that requires entering an email and clicking 'Reset'. Which of these is the best test case title and expected result pair?

hard

A. Reset password; Expected: Password changes immediately

B. Check password reset button; Expected: Button is clickable

C. Password reset test; Expected: Page reloads

D. Test password reset with valid email; Expected: Reset link sent to email

Solution

1. Step 1: Evaluate clarity of test case title

   Test password reset with valid email; Expected: Reset link sent to email clearly states the action and input (valid email) for password reset.

2. Step 2: Check expected result relevance

   Test password reset with valid email; Expected: Reset link sent to email's expected result matches the feature behavior: sending reset link.

3. Final Answer:

   Test password reset with valid email; Expected: Reset link sent to email -> Option D

4. Quick Check:

   Clear title + correct expected result = Test password reset with valid email; Expected: Reset link sent to email [OK]

Hint: Match test title and expected result clearly [OK]

Common Mistakes:

• Using vague titles
• Wrong expected results
• Ignoring feature behavior