compatibility testing:See interoperability testing. orderange complete testing:See exhaustive testing completion criteria:See exit criteria. complexity:The degree to which a component or system has a design and/or internal structure that is difficult to understand,maintain and verify.See also cyclomatic complexity. nce:Th capab the software produ adhere to standards,conventions or regulations in laws and similar prescriptions.[SO9126] compliance testing:The process of testing to determine the compliance of the component or system. component:A minimal software item that can be tested in isolation. component integration testing:Testing performed to expose defects in the interfaces and interaction between integrated components. s of its componen specifeation:A descrption of a component's functon in term e under specif itions,and required non-function component testing:The testing of individual software components.[After IEEE610] compound condition:Two or more single conditions joined by means of a logical operator (AND,OR or XOR),e.g.'A>B AND C>1000 concrete test case:See low level test case testing:Testing to how the activities within the inte al ved ei handled by th como vities or by ent o or system.[] condition:A logical expression that can be evaluated as True or False,e.g.A>B.See also test condition. condition combination coverage:See multiple condition coverage condition combination testing:See multiple condition testing. condition coverage:The percentage of condition outcomes that have bee exercised by a test suite.100%condition coverage requires ach singe condition in very decision statement to be tested as True and False condition determination coverage:The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100%condition determination coverage implies 100%decision condition coverage. condition determination testing:A w to execute condition testing:A white box test design technique in which test cases are designed to execute condition outcomes. condition outcome:The evaluation of a condition to True or False 1212 compatibility testing: See interoperability testing. compiler: A software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610] complete testing: See exhaustive testing. completion criteria: See exit criteria. complexity: The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify. See also cyclomatic complexity. compliance: The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions. [ISO 9126] compliance testing: The process of testing to determine the compliance of the component or system. component: A minimal software item that can be tested in isolation. component integration testing: Testing performed to expose defects in the interfaces and interaction between integrated components. component specification: A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non-functional behavior (e.g. resource-utilization). component testing: The testing of individual software components. [After IEEE 610] compound condition: Two or more single conditions joined by means of a logical operator (AND, OR or XOR), e.g. ‘A>B AND C>1000’. concrete test case: See low level test case. concurrency testing: Testing to determine how the occurrence of two or more activities within the same interval of time, achieved either by interleaving the activities or by simultaneous execution, is handled by the component or system. [After IEEE 610] condition: A logical expression that can be evaluated as True or False, e.g. A>B. See also test condition. condition combination coverage: See multiple condition coverage. condition combination testing: See multiple condition testing. condition coverage: The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False. condition determination coverage: The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% condition determination coverage implies 100% decision condition coverage. condition determination testing: A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome. condition testing: A white box test design technique in which test cases are designed to execute condition outcomes. condition outcome: The evaluation of a condition to True or False