Testing in the software development lifecycle in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of testing in the software development lifecycle?

Testing helps find and fix problems early to make sure the software works well and meets user needs.

beginner

Name two common types of testing done during the software development lifecycle.

Unit testing (checks small parts of code) and system testing (checks the whole software together).

intermediate

At which phase of the software development lifecycle should testing start?

Testing should start early, even during the requirements and design phases, to catch issues before coding.

intermediate

What is regression testing and why is it important?

Regression testing checks that new changes do not break existing features. It keeps software stable over time.

intermediate

How does automated testing help in the software development lifecycle?

Automated testing runs tests quickly and often, saving time and catching problems early without manual effort.

When should testing ideally begin in the software development lifecycle?

A After deployment

B Only after coding is complete

C During user training

D During the requirements phase

Testing should start early, even during requirements, to find issues before coding begins.

Which type of testing focuses on checking small parts of the code individually?

A Unit testing

B System testing

C Acceptance testing

D Performance testing

Unit testing checks individual pieces of code to ensure they work correctly.

What is the main goal of regression testing?

A Check if old features still work after changes

B Test new features only

C Test software speed

D Test user interface design

Regression testing ensures that recent changes do not break existing functionality.

How does automated testing benefit the development process?

A It slows down testing

B It requires more manual work

C It runs tests faster and more often

D It replaces all manual testing

Automated testing speeds up testing and allows frequent checks without extra manual effort.

Which phase is NOT typically part of the software development lifecycle where testing occurs?

A Design

B Marketing

C Maintenance

D Deployment

Marketing is outside the software development lifecycle phases where testing happens.

Explain why testing early in the software development lifecycle is beneficial.

Think about how fixing problems early is easier than later.

Describe the difference between unit testing and system testing.

Compare testing a single piece versus the entire product.

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