Test case writing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the test case name.

Testing Fundamentals

test_case_name = "[1]"

Drag options to blanks, or click blank then click option'

AVerify login functionality

BrunTest

C123Test

Dtest-case

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-descriptive names like 'runTest' or numbers.

Including special characters like '-' in the name.

The test case name should be descriptive and meaningful, like "Verify login functionality".

2fill in blank

medium

Complete the code to specify the test case precondition.

Testing Fundamentals

precondition = "[1]"

Drag options to blanks, or click blank then click option'

AVerify the output

BUser is logged in

CClick the submit button

DTest completed

Attempts:

3 left

💡 Hint

Common Mistakes

Writing actions or verification steps as preconditions.

Leaving precondition empty or vague.

The precondition describes the state before the test starts, such as "User is logged in".

3fill in blank

hard

Fix the error in the test step description.

Testing Fundamentals

test_step = "[1]"

Drag options to blanks, or click blank then click option'

AVerify login button

BTest passed

CEnter valid username and password

DUser clicks login

Attempts:

3 left

💡 Hint

Common Mistakes

Using verification or result statements as test steps.

Writing incomplete or unclear actions.

The test step should describe an action clearly, like "Enter valid username and password".

4fill in blank

hard

Fill both blanks to write a valid expected result and test priority.

Testing Fundamentals

expected_result = "[1]"
priority = "[2]"

Drag options to blanks, or click blank then click option'

ALogin successful

BHigh

CLow

DError message displayed

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing expected results with priority values.

Using vague expected results.

The expected result should describe the correct outcome, like "Login successful". The priority indicates importance, such as "High".

5fill in blank

hard

Fill all three blanks to complete the test case dictionary with name, steps, and expected result.

Testing Fundamentals

test_case = {
  "name": "[1]",
  "steps": ["[2]"],
  "expected_result": "[3]"
}

Drag options to blanks, or click blank then click option'

AVerify password reset

BClick reset password link

CPassword reset email sent

DOpen homepage

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated steps or results.

Leaving any field empty or unclear.

The test case dictionary includes a descriptive name, a clear test step, and the expected result.

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