Browsing by Author "Visser, Willem"
Now showing 1 - 3 of 3
- Results Per Page
- Sort Options
Item FITE: Future Integrated Testing Environment(ACM, 2010) Whalen, Michael; Godefroid, Patrice; Mariani, Leonardo; Polini, Andrea; Tillman, Nikolai; Visser, WillemIt is well known that the later software errors are discovered during the development process, the more costly they are to repair, yet testing and automated analysis tools tend to be applied late in the development cycle. In this paper, we describe a future integrated testing environment (FITE) that continually analyzes code for a variety of functional and non-functional properties to provide developer feedback as code is being written. This instant feedback allows developers to fix errors as they are introduced, increasing developer productivity and software quality.Item Specification Centered Testing(2001) Heimdahl, Mats; Rayadurgam, Sanjai; Visser, WillemThis position paper discusses a framework for automating the testing of systems with stringent structural coverage requirements, for example, avionics systems. The framework covers testing of the model of the desired behavior as well as the resulting implementation. We use a formal model of the required software behavior as the central component of our testing strategy; we call this approach specification centered testing. We discuss how a model checker can be used to automatically generate complete test sequences that will provide arbitrary structural coverage of the requirements specification as well as the code implementing the requirements.Item The Hidden Models of Model Checking(Springer, 2012) Visser, Willem; Dwyer, Matthew; Whalen, MichaelIn the past, applying formal analysis, such as model checking, to industrial problems required a team of formal methods experts and a great deal of effort. Model checking has become popular, because model checkers have evolved to allow domain-experts, who lack model checking expertise, to analyze their systems. What made this shift possible and what roles did models play in this? That is the main question we consider here. We survey approaches that transform domain-specific input models into alternative forms that are invisible to the user and which are amenable to model checking using existing techniques—we refer to these as hidden models. We observe that keeping these models hidden from the user is in fact paramount to the success of the domain-specific model checker. We illustrate the value of hidden models by surveying successful examples of their use in different areas of model checking (hardware and software) and how a lack of suitable models hamper a new area (biological systems).