Test case writing in Testing Fundamentals - Framework Patterns

Framework Mode - Test case writing

Folder Structure for Test Case Writing

project-root/
├── test-cases/
│   ├── login_tests.md
│   ├── signup_tests.md
│   └── profile_tests.md
├── test-data/
│   └── user_data.csv
├── test-reports/
│   └── report_2024_06_01.html
└── README.md

This simple structure organizes test cases as markdown files inside test-cases/. Test data is stored separately in test-data/. Reports go to test-reports/.

Test Case Writing Layers

• Test Cases: Written in clear steps describing inputs, actions, and expected results.
• Test Data: Sample data used in test cases, kept separate for easy updates.
• Test Execution: Manual or automated running of test cases to verify software behavior.
• Test Reporting: Documenting results of test execution, pass or fail.
• Review & Maintenance: Regular updates to test cases to keep them relevant and accurate.

Configuration Patterns for Test Case Writing

• Test Case Template: Use a consistent format for all test cases including fields like Test ID, Title, Preconditions, Steps, Expected Result, Actual Result, Status.
• Environment Details: Specify software version, hardware, and environment setup in test case documentation.
• Test Data Management: Keep test data in separate files or tables referenced by test cases.
• Version Control: Store test cases in a version control system (like Git) to track changes over time.

Test Reporting and Integration

• Test Execution Logs: Record pass/fail status and any defects found during test runs.
• Summary Reports: Provide overview of test coverage, number of tests passed/failed, and critical issues.
• Defect Linking: Connect failed test cases to bug tracking tools for easy follow-up.
• Continuous Integration: Integrate test case execution results into CI pipelines for automated feedback.

Best Practices for Test Case Writing

1. Clear and Simple Language: Write test steps so anyone can understand and follow them easily.
2. One Action per Step: Keep each step focused on a single action to avoid confusion.
3. Include Expected Results: Always state what should happen after each step to verify correctness.
4. Reusable Test Cases: Design test cases that can be reused for different data or scenarios.
5. Keep Test Cases Up-to-Date: Regularly review and update test cases to reflect software changes.

Self Check Question

Where in this folder structure would you add a new test case for verifying the password reset feature?

Key Result

Organize clear, simple test cases in dedicated folders with consistent templates and separate test data for easy maintenance and reporting.

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