Software Testing MCQs - Part 2 | Competitive Exam Preparation

1.1 Which testing level is performed by developers?

A) System Testing B) Integration Testing C) Unit Testing D) Acceptance Testing

Correct Answer: C) Unit Testing

Explanation:
Unit Testing is the lowest level of testing where individual components or units of code are tested in isolation. Developers typically perform unit testing as they write the code, often using frameworks like JUnit (Java), NUnit (.NET), or pytest (Python). Other testing levels are usually performed by dedicated testers or QA teams.

1.2 Big Bang Integration Testing refers to:

A) Integrating all modules at once and testing B) Testing modules incrementally C) Testing only the main module D) None of the above

Correct Answer: A) Integrating all modules at once and testing

Explanation:
Big Bang Integration is an approach where all or most of the modules are combined at once and tested as a whole. While simple to implement, it makes defect isolation difficult since failures could be anywhere in the system. The alternative approaches are incremental integration methods like Top-Down or Bottom-Up integration.

1.3 System Testing is performed by:

A) Developers B) Testers C) End Users D) Business Analysts

Correct Answer: B) Testers

Explanation:
System Testing is typically performed by dedicated testers or QA teams, not developers or end users. It evaluates the complete and integrated software system to verify that it meets specified requirements. This level of testing comes after unit and integration testing but before acceptance testing.

1.4 Which testing level validates business requirements?

A) Unit Testing B) Integration Testing C) System Testing D) Acceptance Testing

Correct Answer: D) Acceptance Testing

Explanation:
Acceptance Testing is the final testing level that validates whether the software meets business requirements and is ready for deployment. It's typically performed by end users or business stakeholders and focuses on business workflows rather than technical implementation details.

1.5 Smoke Testing is also known as:

A) Regression Testing B) Build Verification Testing C) Performance Testing D) Stress Testing

Correct Answer: B) Build Verification Testing

Explanation:
Smoke Testing, also called Build Verification Testing or Confidence Testing, is a preliminary test to check whether the most crucial functions of a software build work as expected. It's a shallow but wide test that helps determine if the build is stable enough for more thorough testing.

2.1 A good test case should be:

A) Complex and lengthy B) Traceable to requirements C) Executed only once D) None of the above

Correct Answer: B) Traceable to requirements

Explanation:
A good test case should be clear, concise, and traceable back to specific requirements or user stories. This ensures test coverage of all requirements and helps in impact analysis when requirements change. Test cases should be repeatable (not executed only once) and should avoid unnecessary complexity.

2.2 Which of the following is NOT part of a test case?

A) Test Steps B) Expected Result C) Developer's Name D) Test Data

Correct Answer: C) Developer's Name

Explanation:
A standard test case typically includes: - Test Case ID - Description/Objective - Preconditions - Test Steps - Test Data - Expected Result - Actual Result (after execution) The developer's name is not a standard component of a test case, though the tester's name might be included in some formats.

2.3 Test Case Prioritization helps in:

A) Reducing the number of test cases B) Executing the most critical test cases first C) Removing all test cases D) None of the above

Correct Answer: B) Executing the most critical test cases first

Explanation:
Test Case Prioritization is a technique to order test cases so that the most important or critical tests are executed early in the testing cycle. This helps in early detection of critical defects when time or resources are limited. It doesn't reduce the total number of test cases but optimizes their execution order.

2.4 Which technique is used to derive test cases from requirements?

A) Error Guessing B) Exploratory Testing C) Use Case Testing D) Ad-hoc Testing

Correct Answer: C) Use Case Testing

Explanation:
Use Case Testing is a systematic technique to derive test cases from requirements by analyzing use cases (descriptions of system behavior from an actor's perspective). Each use case scenario (main flow, alternate flows, exception flows) becomes the basis for test cases. The other options are less structured approaches.

2.5 A test case that checks for invalid inputs is an example of:

A) Positive Testing B) Negative Testing C) Performance Testing D) Regression Testing

Correct Answer: B) Negative Testing

Explanation:
Negative Testing involves validating how the system handles invalid, unexpected, or abnormal inputs or conditions. It ensures the system fails gracefully and maintains security/stability when faced with improper usage. Positive Testing, in contrast, verifies expected behavior with valid inputs.

Software Testing MCQs - Part 2

Your Score: /10