| J. C. King. Symbolic execution and program testing. Commun. ACM, 19(7):385--394, 1976. |
....by first selecting a set of paths that covers all the statements satisfying a given criterion and then generating a test input which executes each selected path. These approaches include, among others, symbolic evaluation and program execution based test data generation. Symbolic evaluation [Kin76] consists in replacing input variables by symbolic values. It then derives path constraints over these symbolic values, forming a constraint system describing conditions under which a path is traversed. The constraints are then symbolically solved. Although symbolic evaluation is promising, it ....
J.C. King. Symbolic Execution and Program Testing. Communications of the ACM, 19(7):385--394, July 1976.
....reactive systems. A drawback of model checking is that it su ers from the statespace explosion problem and typically requires a closed system, i.e. a system together with its environment, and a bound on input sizes [4, 6, 9, 19] We present a novel framework based on symbolic execution [14], which automates test case generation, allows model checking concurrent programs that take inputs from unbounded domains with complex structure, and helps combat state space explosion. Symbolic execution is a well known program analysis technique, which represents values of program variables with ....
....a precondition that the input list should be acyclic, the analysis does not consider the three executions (Figure 1) where the input has a cycle. The input structures and constraints can be used for test input generation. 3 Background: Symbolic execution The main idea behind symbolic execution [14] is to use symbolic values, instead of actual data, as input values, and to represent the values of program variables as symbolic expressions. As a result, the output values computed by a program are expressed as a function of the input symbolic values. The state of a symbolically executed ....
[Article contains additional citation context not shown here]
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385-394, 1976.
.... model based testing is typically a model of expected system behavior and can be derived from a number of sources, namely, a model of the requirements, use cases, design specifications of a system [12] even the code itself can be used to create a model (e.g. symbolic execution based approaches [19,21]) As with the dynamic approach, it is most typical to use some notion of coverage of the model to derive test inputs, i.e. generate inputs that cover all transitions (or branches, etc. in the model. To construct a model of the expected system behavior can, however, be a costly process. On the ....
J. C. King. Symbolic Execution and Program Testing. Communications of the ACM, 19(7):385-394, 1976.
....be specified to obtain any form of slice. A conditioned slice can be computed by first simplifying the program with respect to the condition on the input (i.e. discarding infeasible paths with respect to the input condition) and then computing a slice on the reduced program. A symbolic executor [53, 24] can be used to compute the reduced program, also called conditioned program in [15] Although the identification of the infeasible paths of a conditioned program is in general an undecidable problem, in most cases implications between conditions can be automatically evaluated by a theorem prover, ....
J.C. King, "Symbolic execution and program testing", Communications of the ACM, vol. 19, no. 7, 1976, pp. 385-394.
....to be satisfied. Constraints are originally created using the variables that occur in the program text. Unfortunately, this includes variables that are internal to the program, that is, variables that are not given values as part of the test case. For test case generation, symbolic evaluation [Kin76, Off91] is used to rewrite the variables to be in terms of input variables. 2.4 Strategies for Detecting Equivalent Mutants The general strategy for detecting equivalent mutants is to find contradictions in the constraint systems. Because recognizing infeasible constraint systems is generally ....
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King, `Symbolic execution and program testing', Communications of the ACM, 19, (7), 385--394 (1976).
No context found.
J. C. King. Symbolic execution and program testing. Commun. ACM, 19(7):385--394, 1976.
No context found.
J. C. King, Symbolic Execution and program testing. Communications of the ACM, pages 385--394, July 1976.
No context found.
James C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, 1976.
No context found.
J. King. Symbolic execution and program testing. Comm. ACM, 19:385--394, 1976.
No context found.
J. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, 1976.
No context found.
J. C. King. Symbolic Execution and Program Testing. Communications of the ACM, 19(7):385394, 1976.
No context found.
J. C. King. Symbolic execution and program testing. Commun. ACM, 19(7):385--394, 1976.
No context found.
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King. Symbolic Execution and Program Testing. Comm. ACM, 19(7):385--394, 1976.
No context found.
J. C. King, Symbolic execution and program testing, Communications of the ACM 19 (7) (1976) 385--394.
No context found.
J. King. Symbolic execution and program testing. Comm. ACM, 19:385--394, 1976.
No context found.
J. King. Symbolic execution and program testing. Comm. ACM, 19:385--394, 1976.
No context found.
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King. Symbolic execution and program testing. Commun. ACM, 19(7):385{ 394, 1976.
No context found.
James C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. King. Symbolic Execution and Program Testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, July 1976.
No context found.
J. C. King. Symbolic execution and program testing. Communications of the ACM, 19(7):385--394, 1976.
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC