A phone ringing in an adjacent cubicle momentarily distracts a a programmer, causing
him to improperly program the logic that checks the upper boundary of an input variable.
Later, during system testing, a tester notices that this variable accepts input values. The
improperly coded logic for the upper boundary check is :
a.The root cause
b.The error
c.The defect
d.The Failure ** Answ** c
What is quality?
a.Part of quality management focused on providing confidence that quality requirements
will befulfilled
b.The degree to which a component, system or process meets specified requirements
and/oruser/customer needs and expectations
c.The degree to which a component or system protects information and data so that
persons orother components or systems have the degree of access appropriate to their
types and levelsof authorization.
d.The total costs incurred on quality activities and issues and often split into prevention
costs,appraisal costs, internal failure costs and external failure costs. ** Answ** b
Which of the following is a typical test objective?
a.Preventing defects
b.Repairing defects
c.Comparing actual results to expected results
d.Analyzing the cause of failure ** Answ** a
A product owner says that your role as a tester on an Agile team is to catch all the bugs
before the end of each iteration. Which of the following is a testing principle that could
be used to respond to this statement?
a.Defect clustering
b.Testing shows the presence of defects
c.Absence of error fallacy
d.Root cause analysis ** Answ** b
Programmers often write and execute unit tests against code which they have written.
During this self-testing activity, which of the following is a tester mindset that
programmers should adopt to perform this unit testing effectively?
a.Good communication skills
b.Code coverage
, c.Evaluating code defects
d.Attention to detail ** Answ** d
Consider the following testing activities: 1. Selecting regression tests 2. Evaluating
completeness of test execution 3. Identifying which user stories have open defect
reports 4. Evaluating whether the number of tests for each requirement is consistent
with the level of product risk Consider the following ways traceability can help testing: A.
Improve understandability of test status reports to include status of test basis items B.
Make testing auditable C. Provide information to assess process quality D. Analyze the
impact of changes Which of the following best matches the testing activity with how
traceability can assist that activity?
a.1D, 2B, 3C, 4A
b.1B, 2D, 3A, 4C
c.1D, 2C, 3A, 4B
d.1D, 2B, 3A, 4C ** Answ** d
A tester participated in a discussion about proposed database structure. The tester
identified a potentialperformance problem related to certain common user searches.
This possible problem was explainedto the development team. Which of the following is
a testing contribution to success that BEST matchesthis situation?
a.Enabling required tests to be identified at an early stage
b.Ensuring processes are carried out properly
c.Reducing the risk of fundamental design defects
d.Reducing the risk of untestable functionality ** Answ** c
Which of the following is an example of a task that can be carried out as part of the test
process?
a.Analyzing a defect
b.Designing test data
c.Assigning a version to a test item
d.Writing a user story ** Answ** b
You are running a performance test with the objective of finding possible network
bottlenecks in interfaces between components of a system. Which of the following
statements describes this test?
a.A functional test during the integration test level
b.A non-functional test during the integration test level
c.A functional test during the component test level
d.A non-functional test during the component test level ** Answ** b
Which of the following statements is true?
a.Impact analysis is useful for confirmation testing during maintenance testing
b.Confirmation testing is useful for regression testing during system design
c.Impact analysis is useful for regression testing during maintenance testing
d.Confirmation testing is useful for impact analysis during maintenance testing **
Answ** c