Testing in the software development lifecycle in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

When is integration testing typically performed in the software development lifecycle?

Choose the phase in the software development lifecycle when integration testing is usually done.

A After unit testing and before system testing

B Before unit testing

C After system testing and before acceptance testing

D Only after the software is deployed to production

💡 Hint

Integration testing checks how different parts work together, so it happens after individual parts are tested.

Integration testing is done after unit testing to verify that combined components work together correctly, but before system testing which tests the whole system.

❓ Predict Output

intermediate

What is the output of this test execution report summary?

Given the following test execution summary, what is the total number of failed tests?

Testing Fundamentals

Test Suite: User Login Tests
Tests run: 10
Tests passed: 8
Tests failed: 2
Tests skipped: 0

A 2

B 0

C 10

D 8

💡 Hint

Look for the line that says 'Tests failed'.

The summary clearly states 'Tests failed: 2', so the number of failed tests is 2.

❓ assertion

advanced

Which assertion correctly verifies that a function returns a non-empty list?

Choose the assertion statement that correctly checks if the function get_items() returns a list with at least one item.

Testing Fundamentals

def get_items():
    return ['apple', 'banana']

A assert get_items() == ''

B assert get_items() == []

C assert get_items() is None

D assert len(get_items()) > 0

💡 Hint

Think about how to check the size of a list.

Checking that the length of the list is greater than zero confirms it is not empty. Other options check for empty or None values incorrectly.

🔧 Debug

advanced

Identify the error in this test case code snippet

What error will this test code raise when executed?

Testing Fundamentals

def test_divide():
    result = divide(10, 0)
    assert result == 0

A AssertionError because result is not 0

B NameError because 'divide' function is not defined

C ZeroDivisionError because of division by zero

D No error, test passes

💡 Hint

Check if the function used is defined anywhere.

The code calls 'divide' which is not defined, so Python raises a NameError before any assertion or division happens.

❓ framework

expert

In a CI/CD pipeline, which testing stage should run immediately after code commit to catch errors early?

Choose the testing stage that is best suited to run right after a developer commits code to the repository in a Continuous Integration/Continuous Deployment (CI/CD) pipeline.

A System testing

B User acceptance testing

C Unit testing

D Performance testing

💡 Hint

Think about fast, automated tests that check small pieces of code.

Unit tests run quickly and verify individual components immediately after code changes, helping catch errors early in CI/CD pipelines.

Practice

1. Which phase in the software development lifecycle is primarily responsible for planning how testing will be done?

easy

A. Deployment

B. Coding

C. Requirement Analysis

D. Maintenance

Solution

1. Step 1: Understand the role of Requirement Analysis

   This phase gathers and analyzes what the software should do, including defining test requirements.

2. Step 2: Identify testing planning activities

   Planning how to test is done early, during Requirement Analysis, to ensure tests cover all needs.

3. Final Answer:

   Requirement Analysis -> Option C

4. Quick Check:

   Testing plan starts in Requirement Analysis [OK]

Hint: Testing plans start with requirements, not coding [OK]

Common Mistakes:

• Confusing coding phase with testing planning
• Thinking deployment includes test planning
• Assuming maintenance is for initial test planning

2. Which of the following is the correct syntax to describe a test case in a test plan document?

easy

A. Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully

B. Test Case: Verify login\nResult: Success\nID: 001

C. ID: 001\nTest: Login check\nOutcome: Pass

D. Case Test 1\nCheck login\nExpected: true

Solution

1. Step 1: Identify standard test case format

   Standard test cases include clear ID, description, and expected result fields.

2. Step 2: Compare options to standard format

   Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully matches the clear, structured format; others are incomplete or unclear.

3. Final Answer:

   Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully -> Option A

4. Quick Check:

   Clear ID, description, expected result = Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully [OK]

Hint: Look for clear ID, description, expected result format [OK]

Common Mistakes:

• Using unclear or incomplete test case fields
• Mixing field names or order
• Omitting expected results

3. Consider this code snippet representing a simple test function in Python:

def test_addition():
    result = 2 + 3
    assert result == 5
    print('Test passed')

What will be the output when this test runs?

medium

A. SyntaxError

B. Test passed

C. No output

D. AssertionError

Solution

1. Step 1: Analyze the test function logic

   The function adds 2 + 3, stores 5 in result, then asserts result equals 5, which is true.

2. Step 2: Determine output after assertion

   Since assertion passes, the print statement runs, outputting 'Test passed'.

3. Final Answer:

   Test passed -> Option B

4. Quick Check:

   Assertion true means print runs [OK]

Hint: If assert condition is true, print runs [OK]

Common Mistakes:

• Thinking assertion always raises error
• Expecting no output from print
• Confusing syntax with runtime error

4. A tester wrote this test script snippet:

def test_divide():
    result = 10 / 0
    assert result == 0

What is the main problem with this test?

medium

A. Test function name is incorrect

B. Assertion should check for 10, not 0

C. Missing print statement

D. Division by zero causes runtime error

Solution

1. Step 1: Identify the operation causing error

   Dividing 10 by 0 causes a ZeroDivisionError at runtime.

2. Step 2: Understand impact on test execution

   Because of the error, assertion is never reached and test fails with exception.

3. Final Answer:

   Division by zero causes runtime error -> Option D

4. Quick Check:

   Division by zero = runtime error [OK]

Hint: Division by zero always causes error [OK]

Common Mistakes:

• Ignoring runtime error and focusing on assertion
• Thinking assertion is wrong instead
• Assuming print statement needed

5. In a software project, testing is integrated throughout the lifecycle. Which testing type is best suited to catch issues caused by changes in code after deployment?

hard

A. Regression Testing

B. Unit Testing

C. Acceptance Testing

D. Smoke Testing

Solution

1. Step 1: Understand testing types and their purpose

   Unit Testing checks small code parts; Acceptance Testing checks user needs; Smoke Testing checks basic functionality.

2. Step 2: Identify testing for post-deployment changes

   Regression Testing reruns tests to ensure new changes don't break existing features after deployment.

3. Final Answer:

   Regression Testing -> Option A

4. Quick Check:

   Regression Testing catches post-change issues [OK]

Hint: Regression Testing checks after code changes [OK]

Common Mistakes:

• Confusing unit testing with regression testing
• Thinking acceptance testing covers code changes
• Assuming smoke testing is for detailed checks