1. What is quality?

• Activities focused on providing confidence that quality requirements will be fulfilled.
• The degree to which a component or system satisfies the stated and implied needs of its various stakeholders.
• The degree to which a component or system protects information and data so that persons or other components or systems have the degree of access appropriate to their types and levels of authorization.
• The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.

2. Which of the following is a typical test objective?

• Preventing defects
• Repairing defects
• Comparing actual results to expected results
• Analyzing the cause of failure

3. A phone ringing in an adjac ent cubicle momentarily distracts a programmer, causing the programmer to improperly program the logic that checks the upper boundary of an input variable.

Later, during system testing, a tester notices that this input field accepts invalid input values. The improperly coded logic for the upper boundary check is:

• The root cause
• The failure
• The error
• The defect

4. 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 (false) statement?

• Defect clustering
• Testing shows the presence of defects
• Absence of error fallacy
• Root cause analysis

5. 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?

• Good communication skills
• Code coverage
• Evaluating code defects
• Attention to detail

6. 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?

Traceability assists with:

• 1D, 2B, 3C, 4A
• 1B, 2D, 3A, 4C
• 1D, 2C, 3A, 4B
• 1D, 2B, 3A, 4C

7. A tester participated in a discussion about proposed database structure. The tester identified a potential performance problem related to certain common user searches. This possible problem was explained to the development team.

Which of the following is a testing contribution to success that BEST matches this situation?

• Enabling required tests to be identified at an early stage
• Ensuring processes are carried out properly
• Reducing the risk of fundamental design defects
• Reducing the risk of untestable functionality

8. Which of the following is an example of a task that can be carried out as part of the test process?

• Analyzing a defect
• Designing test data
• Assigning a version to a test item
• Writing a user story

9. 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 functional test during the integration test level
• A non-functional test during the integration test level
• A functional test during the component test level
• A non-functional test during the component test level

10. Which of the following statements is true?

• Impact analysis is useful for confirmation testing during maintenance testing
• Confirmation testing is useful for regression testing during system design
• Impact analysis is useful for regression testing during maintenance testing
• Confirmation testing is useful for impact analysis during maintenance testing