Why Test case writing in Testing Fundamentals? - Purpose & Use Cases

The Big Idea

What if you could catch hidden bugs every time by simply writing down your testing steps?

The Scenario

Imagine you have a big app with many features. You try to check each feature by clicking around and guessing what might break.

You write notes on paper or in random files about what you tested.

Later, you forget what you tested or how you tested it.

The Problem

Manual testing like this is slow and tiring.

You can easily miss important steps or forget to check some parts.

It's hard to repeat tests exactly the same way every time.

When bugs appear, you don't know what was tested before or how.

The Solution

Writing clear test cases solves these problems.

Test cases are simple step-by-step instructions that anyone can follow to check a feature.

They help you test thoroughly, remember what you did, and repeat tests easily.

Before vs After

✗ Before

Check login by trying random usernames and passwords.
Write notes in a notebook.

✓ After

Test Case: Login Function
1. Open login page
2. Enter valid username and password
3. Click login
4. Verify user is logged in

What It Enables

With test case writing, you can test software confidently and catch bugs before users do.

Real Life Example

A team releases a new app update. Thanks to detailed test cases, testers quickly check all features and find a critical bug before launch.

Key Takeaways

Manual testing is slow and forgetful without clear steps.

Test case writing creates repeatable, clear instructions for testing.

This helps find bugs early and improves software quality.

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