Specifying and checking method call sequences of Java programs

Cheon, Yoonsik; Perumandla, Ashaveena

doi:10.1007/s11219-006-9001-4

Cited by 35 publications

(43 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As an important consequence, no change in the implementation of the statebased assertion checker is needed, in contrast to the following works. Cheon and Perumandla present in [6] an extension of the JML compiler with call sequence assertions. Call sequence assertions are regular expressions (proper context-free grammars cannot be handled) over method names and the data sent in calls and returns is not considered.…”

Section: Resultsmentioning

confidence: 99%

Run-Time Assertion Checking of Data- and Protocol-Oriented Properties of Java Programs: An Industrial Case Study

Boer

Gouw

Johnsen

et al. 2014

Transactions on Aspect-Oriented Software Development XI

View full text Add to dashboard Cite

Abstract. Run-time assertion checking is one of the useful techniques for detecting faults, and can be applied during any program execution context, including debugging, testing, and production. In general, however, it is limited to checking state-based properties. We introduce SAGA, a general framework that provides a smooth integration of the specification and the run-time checking of both data-and protocoloriented properties of Java classes and interfaces. We evaluate SAGA, which combines several state of the art tools, by conducting an industrial case study from an eCommerce software company Fredhopper.

show abstract

Section: Resultsmentioning

confidence: 99%

Run-Time Assertion Checking of Data- and Protocol-Oriented Properties of Java Programs: An Industrial Case Study

Boer

Gouw

Johnsen

et al. 2014

Transactions on Aspect-Oriented Software Development XI

View full text Add to dashboard Cite

show abstract

“…As an example, one can use regular expressions to specify the order in which functions or methods in a program should be called [18]. Such specifications describe the control-flow of the program.…”

Section: Run-time Checking Of Object-oriented Programsmentioning

confidence: 99%

“…As a specification language for object-oriented programs, regular expressions can be used to denote valid histories [18]. In this setting, the alphabet symbols correspond to method names, histories are represented as sequences of such alphabet symbols, and the valid histories are the words of the regular language.…”

Section: Regular Expressionsmentioning

confidence: 99%

“…There is a wide range of specification languages used in run-time verification. They can be partitioned into two categories: languages that focus on the control-flow (these approaches are also called "monitoring"), and those focussing on data-flow.As an example, one can use regular expressions to specify the order in which functions or methods in a program should be called [18]. Such specifications describe the control-flow of the program.…”

mentioning

confidence: 99%

“…As an example, the regular expression (ab) * denote the language of all words starting with "a" in which "a" and "b" alternate. The formal properties of regular languages have been widely studied in the field of formal languages and theory of computation, see for example the books [65,51].As a specification language for object-oriented programs, regular expressions can be used to denote valid histories [18]. In this setting, the alphabet symbols correspond to method names, histories are represented as sequences of such alphabet symbols, and the valid histories are the words of the regular language.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Combining Monitoring with Run-Time Assertion Checking

Boer

Gouw

2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. According to a study in 2002 commisioned by a US Department, software bugs annually costs the US economy an estimated $59 billion 1 . A more recent study in 2013 by Cambridge University estimated that the global cost has risen to $312 billion globally 2 .There exists various ways to prevent, isolate and fix software bugs, ranging from lightweight methods that are (semi)-automatic, to heavyweight methods that require significant user interaction. Our own method described in this tutorial is based on automated run-time checking of a combination of protocol-and data-oriented properties of object-oriented programs. Run-Time Checking of Object-Oriented ProgramsGiven a program and a specification, a run-time verifier inserts checks in the code that determine whether the specification is satisfied. The checks are triggered during an actual execution of the program. In contrast to static verification, where properties are checked with respect to all executions (possibly there are infinitely many), run-time checkers only consider a single execution of the program. There is a wide range of specification languages used in run-time verification. They can be partitioned into two categories: languages that focus on the control-flow (these approaches are also called "monitoring"), and those focussing on data-flow.As an example, one can use regular expressions to specify the order in which functions or methods in a program should be called [18]. Such specifications describe the control-flow of the program. Other formalisms for specifying controlflow are temporal logics, various kinds of automata and context-free grammars. For these formalisms, checking whether a given property holds of the current execution involves parsing a word (where the word is some representation of the trace of method calls in the current execution) in an automata. Generally only formalisms are chosen with a decidable parsing problem (in particular, this is the case for regular expressions, context-free grammars and most automata), so Approaches that specify data-flow usually do so by annotating the source code with assertions: logical formulas that must be true whenever control passes them. The formulas constrain the values of the program variables. If assertions are expressed in first-order logic with arithmetic, it is in general undecidable due to unbounded quantification (i.e. ranging over an infinite number of values) whether the assertion is true, thus usually the assertions are restricted in some way. For instance, Java contains an assert-statement which restricts to quantifier-free formulas (i.e. Boolean expressions). Design by Contract [53] provides a systematic way of using assertions to specify classes, interfaces and methods with respectively class invariants and pre-and postconditions. It was first used in the programming language Eiffel, and subsequently has also been applied to many other programming languages. For example, JML [14] is one of the most popular specification languages for Java and supports Design by Contract. JML...

show abstract

Conformance test development with the Java modeling language

Søndergaard

Korsholm

Ravn

2017

Concurrency and Computation

View full text Add to dashboard Cite

In order to claim conformance with a Java Specification Request, a Java implementation has to pass all tests in an associated Technology Compatibility Kit. This paper presents a model-based development of a Technology Compatibility Kit test suite and a test execution tool for the draft safety-critical Java profile specification. The Java Modeling Language is used to model conformance constraints for the profile. Java Modeling Language annotations define contracts for classes and interfaces. The annotations are translated by a tool into runtime assertion checks. Hereby, the design and elaboration of the concrete test cases are simplified, because the expected results are derived from contracts and thus do not need to be provided explicitly. Bottom-up testing is applied for testing methods of the safety-critical Java classes, whereas topdown testing is applied for testing global properties, such as protocols, memory management, and real-time properties, including scheduling. The tests are executed using a simplified version of JUnit, which makes the test suite executable on resource-constrained platforms. Furthermore, Section 2 gives an overview of SCJ and its three conformance levels and concludes with a short overview of Java Modeling Language (JML).It is probably impossible to develop a test suite without familiarity with the language being tested. In our case, we have followed the development of the SCJ specification closely, commented on intermediate draft specifications and, over the years, acquired considerable insight in the details of the specification, as we have developed several prototype implementations [4][5][6]; the most recent one includes all three SCJ levels [7,8].This implementation is developed for resource-constrained embedded platforms, specifically the hardware-near virtual machine (HVM) [9]. Other prototype implementations are [6, 10,11].The draft specification work has nearly finished now (September 2016), although it has been delayed by a combined effort to revise the Real-Time Specification for Java (RTSJ) [12] to version 2.0. Because SCJ builds on RTSJ, this has led to many last minute changes to the SCJ specification. Yet, in order to complete the JSR process for SCJ, we began working on the TCK component in early 2013 [13] and reported on our progress in [14]. This paper consolidates the work of these papers and reports on the most recent progress with building the TCK. Furthermore, the approach is related to model-based testing in general, so it should be of interest for other developers of suites for conformance testing.A TCK is first of all a suite of tests checking whether an implementation of the SCJ technology conforms to the SCJ specification. Of course, the test suite must be based on the SCJ specification only and not be tailored for a particular implementation of the SCJ technology. The specification is written in natural language (English), where the detailed behavior of Java constructs such as classes and methods is documented in the Javadoc standard format.Writing test cod...

show abstract

Specifying and checking method call sequences of Java programs

Cited by 35 publications

References 16 publications

Run-Time Assertion Checking of Data- and Protocol-Oriented Properties of Java Programs: An Industrial Case Study

Run-Time Assertion Checking of Data- and Protocol-Oriented Properties of Java Programs: An Industrial Case Study

Combining Monitoring with Run-Time Assertion Checking

Conformance test development with the Java modeling language

Contact Info

Product

Resources

About