CSE 565 Midterm Exam (Latest Update
) Questions with Correct
Answers {Grade A}100% Verified
Specification Testing - correct answer Black box testing where you evaluate inputs
and outputs but do not look inside the code
Static testing - correct answer Traditional, requirements driven testing. Mainly
performs verification
Behavioral Testing - correct answer Scenario based-testing where all functional
requirements are captured in use-cases. Performs validation & verification
Use cases construction steps - correct answer 1. Identify the actors (can be humans or
subsystems) to determine the scope of the system.
2. For each actor, identify how the actor will use the system to accomplish its functions
3. Detail each use-case identifying each of the flows as a scenario.
,T/F: Use cases can find cracks in the requirements. - correct answer True.
T/F: Use cases should be motivating, encapsulate every scenario, complex, and be easy
to evaluate - correct answer False. They should be motivating, credible (likely to
happen), complex, and easy to evaluate.
Equivalence partitioning steps - correct answer 1. For each input, identify set of
equivalence partitions & label them
2. Write test cases to cover as many uncovered valid equivalence partitions as
possible
3. For each invalid, equivalence partition, write ONE test case for each uncovered
partition
,Equivalence partitioning - correct answer Technique for diving input domain of a
program into a finite number of equivalence partitions (both valid and invalid partitions
are considered)
Verification - correct answer Are we building the product right?
Validation - correct answer Are we building the right product?
Reliability - correct answer The probability that a software program operates for some
given time period without a software error
TDD Phases - correct answer Red, Green, Refactor
Error - correct answer Mistake made by a human
Defect / Fault - correct answer Result of an error from the code
Failure - correct answer Software doesn't do what it is supposed to do
, Unit / Component Testing - correct answer Does the code do what it is supposed to do?
Integration Testing - correct answer Testing features
Systems Testing - correct answer Hardware/software integration (functional & non-
functional testing on security, usability, and safety)
Acceptance Testing - correct answer Customer testing
Beta Testing - correct answer Preferred testing
Functional Testing - correct answer Testing the way the user will be using the system.
Both verification and validation. Applicable at every testing level.
Non-functional testing - correct answer Is it usable and safe? Applicable at higher
levels of testing.
) Questions with Correct
Answers {Grade A}100% Verified
Specification Testing - correct answer Black box testing where you evaluate inputs
and outputs but do not look inside the code
Static testing - correct answer Traditional, requirements driven testing. Mainly
performs verification
Behavioral Testing - correct answer Scenario based-testing where all functional
requirements are captured in use-cases. Performs validation & verification
Use cases construction steps - correct answer 1. Identify the actors (can be humans or
subsystems) to determine the scope of the system.
2. For each actor, identify how the actor will use the system to accomplish its functions
3. Detail each use-case identifying each of the flows as a scenario.
,T/F: Use cases can find cracks in the requirements. - correct answer True.
T/F: Use cases should be motivating, encapsulate every scenario, complex, and be easy
to evaluate - correct answer False. They should be motivating, credible (likely to
happen), complex, and easy to evaluate.
Equivalence partitioning steps - correct answer 1. For each input, identify set of
equivalence partitions & label them
2. Write test cases to cover as many uncovered valid equivalence partitions as
possible
3. For each invalid, equivalence partition, write ONE test case for each uncovered
partition
,Equivalence partitioning - correct answer Technique for diving input domain of a
program into a finite number of equivalence partitions (both valid and invalid partitions
are considered)
Verification - correct answer Are we building the product right?
Validation - correct answer Are we building the right product?
Reliability - correct answer The probability that a software program operates for some
given time period without a software error
TDD Phases - correct answer Red, Green, Refactor
Error - correct answer Mistake made by a human
Defect / Fault - correct answer Result of an error from the code
Failure - correct answer Software doesn't do what it is supposed to do
, Unit / Component Testing - correct answer Does the code do what it is supposed to do?
Integration Testing - correct answer Testing features
Systems Testing - correct answer Hardware/software integration (functional & non-
functional testing on security, usability, and safety)
Acceptance Testing - correct answer Customer testing
Beta Testing - correct answer Preferred testing
Functional Testing - correct answer Testing the way the user will be using the system.
Both verification and validation. Applicable at every testing level.
Non-functional testing - correct answer Is it usable and safe? Applicable at higher
levels of testing.
