Testing Scenario Implementation with Behavior Contracts

Abstract

This paper presents behavior contracts as a new assertion mechanism and a tool that uses such contracts to support the testing of Object-Oriented (OO) systems. A behavior contract models how the scenarios for performing a designated task are expected to be implemented. Based on this contract, our tool can automatically monitor the program execution for checking important properties related to these scenarios. This capability can help testers to determine whether the scenarios have been implemented correctly. Our tool can also collect test coverage information w.r.t. the scenarios modeled by a behavior contract. Such information can be used to direct the testing efforts towards the less-covered scenarios, and to determine whether the implementation of these scenarios has been adequately tested. Therefore, using this tool should improve both the efficiency and effectiveness of testing OO systems.

Correspondence validation method for GUI operations and scenarios by operation history analysis

“…Liang and Xu proposed a method for validating software developed along with scenarios [15]. In this method, scenarios are described using extended sequence diagrams, and a system that monitors the execution of the software is generated using the sequence diagrams.…”

“…To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. IUI'08, January [13][14][15][16]2008, Maspalomas, Gran Canaria, Spain.…”

Testing and verification in service‐oriented architecture: a survey

“…With the use of contracts, some unexpected behaviour of the SUT can be detected, and the information from contracts can also be used to enhance the testing process itself. Software testing using contracts has been applied to traditional software by many researchers .…”