Free Software Testing and Quality Assurance MCQs with Answers

181 Software Testing and Quality Assurance MCQs from Software Engineering, each with the correct answer and a written explanation of why it is correct. Free and unlimited, with no account needed.

Last updated

181 questions · page 2 of 10

  • A. Non-Code Source Statement
  • B. Non Comment Source Sentence
  • C. Non-Comment Source Statement
  • D. All of the mentioned

Explanation: NCSS means Non-Comment Source Statements, counting executable or source statements while excluding comments.

Correct answer: Non-Comment Source Statement
  • A. Code Inspector
  • B. Static Analyzer
  • C. Standard Enforcer
  • D. Coverage Analyzer

Explanation: A static analyzer examines source code systematically and automatically without executing the program, detecting defects and rule…

Correct answer: Static Analyzer
  • A. Static Testing Tool
  • B. Dynamic Testing
  • C. Static & Dynamic Testing
  • D. None of the mentioned

Explanation: A standard enforcer checks source code against rules without running the program, so it is a static testing tool.

Correct answer: Static Testing Tool
  • A. Acceptance testing
  • B. Regression testing
  • C. Equivalence partitioning
  • D. Quality assurance

Explanation: Equivalence partitioning divides inputs into classes expected to behave similarly, allowing representative values to test each class.

Correct answer: Equivalence partitioning
  • A. maintenance
  • B. design
  • C. coding
  • D. documentation

Explanation: Early and effective testing finds defects before release, when they are cheaper to fix, and therefore reduces later maintenance costs.

Correct answer: maintenance
  • A. Yellow box
  • B. White box
  • C. Gray box
  • D. Black box

Explanation: Cyclomatic complexity is calculated from a program's control-flow graph and helps derive independent execution paths, making it a…

Correct answer: White box
  • A. Control structure testing
  • B. Complex path testing
  • C. Code coverage
  • D. Quality assurance of software

Explanation: Code coverage measures which statements, branches, or paths are exercised by the test suite, showing whether the tests actually execute…

Correct answer: Code coverage
  • A. Test case
  • B. Output
  • C. Software Version
  • D. LOC

Explanation: A bug report normally records the test case, observed output, and software version so the fault can be reproduced.

Correct answer: LOC
  • A. Step Over
  • B. Step Into
  • C. Step Up
  • D. Step Out

Explanation: Step Into, Step Over, and Step Out are standard debugger execution commands.

Correct answer: Step Up
  • A. errors
  • B. failures
  • C. bugs
  • D. defects

Explanation: A bug is a mistake or flaw introduced into software during development, especially coding, that may produce incorrect behavior.

Correct answer: bugs
  • A. Mutation analysis
  • B. Validation
  • C. Verification
  • D. Performance analysis

Explanation: Mutation analysis evaluates test-case quality by making small changes, or mutants, in the program and checking whether the tests detect…

Correct answer: Mutation analysis
  • A. Unit testing
  • B. Integration testing
  • C. System testing
  • D. None of the mentioned

Explanation: In object-oriented testing, unit testing treats the smallest testable unit as an encapsulated class or object.

Correct answer: Unit testing
  • A. cluster testing
  • B. thread-based testing
  • C. use-based testing
  • D. none of the mentioned

Explanation: Thread-based testing integrates the classes needed to respond to one system input or event, so it follows an execution thread through…

Correct answer: thread-based testing
  • A. Yellow-box testing
  • B. Black-box testing
  • C. White-box testing
  • D. All of the mentioned

Explanation: Validation testing checks whether the completed software satisfies its requirements, so it is primarily driven by black-box methods that…

Correct answer: Black-box testing
  • A. Fault-based testing
  • B. Integration testing
  • C. Use-based testing
  • D. Scenario-based testing

Explanation: Fault-based testing derives test cases from plausible faults in the OO design or implementation, aiming to expose those specific defects.

Correct answer: Fault-based testing
  • A. Recovery testing
  • B. Stress testing
  • C. System testing
  • D. Random testing

Explanation: Recovery and stress testing are established forms of system testing, while random testing is not normally listed among the standard…

Correct answer: Random testing
  • A. Regression Testing
  • B. Integration testing
  • C. Smoke testing
  • D. Validation testing

Explanation: Smoke testing is a short, broad integration check used to determine whether a build is stable enough for more detailed testing.

Correct answer: Smoke testing
  • A. Use effective formal technical reviews as a filter prior to testing
  • B. Develop a testing plan that emphasizes "rapid cycle testing."
  • C. State testing objectives explicitly
  • D. All of the mentioned

Explanation: A sound strategy states explicit objectives, uses formal reviews before testing, and plans rapid testing cycles so defects are found and…

Correct answer: All of the mentioned
  • A. Integration testing
  • B. Unit testing
  • C. Completion of Testing
  • D. Regression Testing

Explanation: Unit testing is normally performed alongside coding because each newly written unit can be checked in isolation before integration.

Correct answer: Unit testing
  • A. instantaneous test group
  • B. integration testing group
  • C. individual testing group
  • D. independent test group

Explanation: ITG commonly means Independent Test Group, a group separate from the developers that performs testing to provide greater objectivity.

Correct answer: independent test group