Automated Testing via Inferred Properties自动化测试通过推断性质.pptVIP

Symstra: A Framework for Generating Object-Oriented Unit Tests using Symbolic Execution Tao Xie, Darko Marinov, Wolfram Schulte, and David Notkin Motivations Object-oriented unit tests consist of sequences of method invocations. Behavior of an invocation depends on the method’s arguments and the state of the receiver at the beginning of the invocation. Automated test-input generation needs to produce: Method sequences building relevant receiver object states Relevant method arguments Motivations Object-oriented unit tests consist of sequences of method invocations. Behavior of an invocation depends on the method’s arguments and the state of the receiver at the beginning of the invocation. Automated test-input generation needs to produce: Method sequences building relevant receiver object states Relevant method arguments Outline Motivations Example Test generation by exploring concrete states Symstra: exploring symbolic states Evaluation Conclusion Binary Search Tree Example public class BST implements Set { Node root; int size; static class Node { int value; Node left; Node right; } public void insert (int value) { … } public void remove (int value) { … } public bool contains (int value) { … } public int size () { … } } Previous Test-Generation Approaches Straightforward approach: generate all (bounded) possible sequences of calls to the methods under test too many and many are redundant [Xie et al. 04] Concrete-state exploration approach [Willem et al. 04, Xie et al. 04] assume a given set of method call arguments explore new receiver-object states with method calls (in breadth-first manner) Exploring Concrete States Method arguments: insert(1), insert(2), insert(3), remove(1), remove(2), remove(3) Exploring Concrete States Method arguments: insert(1), insert(2), insert(3), remove(1), remove(2), remove(3) Exploring Concrete States Method arguments: insert(1), insert(2), insert(3), remove(1), remove(2), remove(3) Generating