A.A metric for the ratio of statements in a source code that are executed at least once during the test.

B.A method by which complex statements of the source code are completely executed.

C.A test technique that generates a minimal set of tests cases guaranteed to exercise all the lines in source code.

D.A tool used to execute all the statements of the source code.

A.Undefined variables

B.Infinite tools

C.Wrong business rules

D.Syntax errors of the code

A.Tests designed by the author; tests designed by another member of the development team; tests designed by someone from a different company.

B.Tests designed by someone from a different department within the company; tests designed by the author; tests designed by someone from a different company.

C.Tests designed by someone from a different company; tests designed by someone from a different department within the company; tests designed by another member of the development team.

D.Tests designed by someone from a different department within the company; tests designed by someone from a different company; tests designed by the author.

A.The overall process of testing a system to verify that it meets specified requirements.

B.An approach to testing to reduce the level of product risks by focusing on high-risk areas in the product

C.The process of selecting test techniques to exercise the functions implemented by the tested system

D.The process of transforming general testing objectives into tangible test conditions and test cases

A.Testing tools can be used by both developers and testers

B.Testing tools allow developers do testing. Use of such tools changes the role of the test team

C.Intrusive test tools are that do not exhibit the probe-effect

D.Use of testing tools is effective only when done as part of a test automation system