Test case writing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Preconditions in Test Cases

Why are preconditions important in writing test cases?

A They describe the initial state required before test execution.

B They define the cleanup activities after test execution.

C They specify the steps to execute the test case.

D They list the expected results after test execution.

💡 Hint

Think about what must be true before you start testing.

Preconditions set the stage by describing what must be true before the test runs, ensuring consistent test execution.

❓ assertion

intermediate

Correct Assertion for Login Success

Which assertion correctly verifies a successful login by checking the presence of a welcome message?

Testing Fundamentals

welcome_message = get_element_text('welcome-msg')

A assert welcome_message == 'Welcome, user!'

B assert welcome_message != 'Welcome, user!'

C assert welcome_message is None

D assert welcome_message == ''

💡 Hint

The welcome message should exactly match the expected greeting.

The assertion checks that the welcome message text equals the expected string, confirming login success.

🔧 Debug

advanced

Identify the Missing Test Case Element

Review this test case snippet and identify what is missing for a complete test case.

Test Case: Verify password reset functionality
Steps:
1. Navigate to login page
2. Click 'Forgot Password'
3. Enter registered email
4. Submit request
Expected Result: Password reset email is sent

A Test steps are missing

B Test data is missing

C Test case ID is missing

D Expected result is missing

💡 Hint

Think about what input is needed to perform the test.

The test case does not specify the actual email address to use, which is essential test data.

❓ framework

advanced

Best Practice for Test Case Organization in Automation Framework

In an automation framework, how should test cases be organized for maintainability?

A Store test cases only in the test execution report

B Place all test cases in a single file for easy access

C Organize test cases randomly to avoid bias

D Group test cases by feature or functionality modules

💡 Hint

Think about how grouping helps when the application grows.

Grouping test cases by feature or module improves clarity and makes maintenance easier as the project scales.

❓ Predict Output

expert

Test Case Execution Result Analysis

Given the following test case execution log snippet, what is the final test status?

Test Case: Verify user logout
Step 1: Click logout button - Passed
Step 2: Check login page displayed - Failed (Element not found)
Step 3: Verify session ended - Skipped

A Skipped

B Passed

C Failed

D Blocked

💡 Hint

If any step fails, what is the overall test result?

Since one step failed, the entire test case is marked as failed regardless of other steps.

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