|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
An operational profile is a quantification of the expected use of a software component that is used for generating test cases in statistical testing. Previous work on operational profiles has concentrated on exploring the occurrence of operations and little has been said about operation parameters. The testing is meaningless if values for input parameters are not consistent according to the expected use. This paper presents a method for defining parameter characteristics by deriving constraints on and relationships between operation parameters. The parameter characteristics are then used to support generation of appropriate values for input parameters of operations. The method applies formal concept analysis using the component API to derive relationships between operations and parameters. Then the method uses these relationships, usage data and intended usage assumptions for defining characteristics of parameters. The method is illustrated on two Java classes but can be applied to any software component that is accessed through an API. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
General Terms:
Keywords:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||