Test case writing in Testing Fundamentals - Full Explanation

Introduction

Imagine trying to check if a new phone works well without a clear plan. Without steps to follow, you might miss important problems. Test case writing solves this by giving a clear, step-by-step guide to check if something works as expected.

Explanation

Purpose of Test Cases

Test cases help testers know exactly what to check and how to check it. They make sure that every part of the product is tested carefully and nothing important is missed. This helps find problems early before users see them.

Test cases guide testing to find problems and ensure quality.

Components of a Test Case

A test case usually includes a title, description, steps to perform, expected results, and actual results. These parts help anyone understand what to do and what outcome to expect. Clear components make testing consistent and repeatable.

Clear parts in a test case make testing easy to follow and reliable.

Writing Effective Test Cases

Good test cases are simple, clear, and focused on one thing at a time. They use easy language and avoid unnecessary details. Writing effective test cases saves time and helps testers find bugs faster.

Simple and clear test cases improve testing efficiency.

Types of Test Cases

Test cases can be positive, checking if something works as expected, or negative, checking how the system handles wrong inputs or errors. Both types are important to ensure the product is strong and reliable.

Positive and negative test cases together ensure thorough testing.

Benefits of Test Case Writing

Writing test cases helps teams communicate clearly about what to test. It also creates a record that can be reused for future testing or when fixing bugs. This saves time and improves product quality over time.

Test cases improve communication and save time in testing.

Real World Analogy

Think of test cases like a recipe for baking a cake. The recipe lists ingredients, steps, and what the cake should look like when done. Following the recipe helps anyone bake the cake correctly and notice if something goes wrong.

Purpose of Test Cases → The recipe's goal to make a perfect cake every time

Components of a Test Case → Ingredients list, step-by-step instructions, and expected cake appearance

Writing Effective Test Cases → Clear and simple recipe instructions that anyone can follow

Types of Test Cases → Testing with correct ingredients (positive) and checking what happens if you add salt instead of sugar (negative)

Benefits of Test Case Writing → Having the recipe saved to bake the cake again or teach others

Diagram

Diagram

┌─────────────────────────────┐
│        Test Case Writing     │
├─────────────┬───────────────┤
│ Components  │ Purpose       │
│ - Title     │ - Guide tests │
│ - Steps     │ - Find bugs   │
│ - Expected  │               │
├─────────────┴───────────────┤
│ Types of Test Cases          │
│ - Positive                  │
│ - Negative                  │
├─────────────────────────────┤
│ Benefits                    │
│ - Clear communication      │
│ - Reusable records         │
└─────────────────────────────┘

This diagram shows the main parts of test case writing: components, purpose, types, and benefits.

Key Facts

Test Case → A detailed set of steps to check if a feature works correctly.

Positive Test Case → A test case that checks if the system works as expected with valid input.

Negative Test Case → A test case that checks how the system handles invalid or unexpected input.

Expected Result → The outcome that should happen if the system works correctly.

Actual Result → The outcome observed when the test case is executed.

Code Example

Testing Fundamentals

def test_login_with_valid_credentials():
    username = "user1"
    password = "pass123"
    result = login(username, password)
    assert result == "Login successful"

def test_login_with_invalid_password():
    username = "user1"
    password = "wrongpass"
    result = login(username, password)
    assert result == "Login failed: Incorrect password"

Common Confusions

Test cases are only needed for big projects.

Test cases are only needed for big projects. Test cases are useful for projects of all sizes because they help catch errors early and save time regardless of project scale.

Test cases must be very long and detailed.

Test cases must be very long and detailed. Effective test cases are clear and concise, focusing on one thing at a time to avoid confusion.

Only positive test cases are important.

Only positive test cases are important. Both positive and negative test cases are important to ensure the system works well and handles errors gracefully.

Summary

Test case writing provides clear steps to check if a product works correctly and helps find problems early.

Good test cases are simple, clear, and include both positive and negative scenarios for thorough testing.

Writing test cases improves communication among team members and creates reusable testing records.

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