This paper describes a technique that selects, from a large set of test inputs, a small subset
likely to reveal faults in the software under test. The technique takes a program or software …

To find defects in software, one needs test cases that execute the software systematically,
and oracles that assess the correctness of the observed behavior when running these test …

In an object-oriented program, a unit test often consists of a sequence of method calls that
create and mutate objects, then use them as arguments to a method under test. It is …

A test case consists of two parts: a test input to exercise the program under test and a test
oracle to check the correctness of the test execution. A test oracle is often in the form of …

We present an approach for describing tests using non-deterministic test generation
programs. To write such programs, we introduce UDITA, a Java-based language with non …

Program testing is expensive and labor-intensive, often consuming more than half of the
total development costs, and yet it is frequently not done well and the results are not always …

State-of-the art techniques for automated test generation focus on generating executions
that cover program behavior. As they do not generate oracles, it is up to the developer to …

The object‐orientated paradigm provides the power for software development but at the
same time introduces some brand new problems. One of these problems is that the …

Extensible typesafe systems, such as Java, rely critically on a large and complex software
base for their overall protection and integrity, and are therefore difficult to test and verify …

We show how model checking and symbolic execution can be used to generate test inputs
to achieve structural coverage of code that manipulates complex data structures. We focus …