Testing context-sensitive middleware-based software applications

Abstract

During the testing of context-sensitive middleware-based software, the middleware checks the current situation to invoke the appropriate functions of the applications. Since the middleware remains active and the situation may continue to evolve, however, the conclusion of some test cases may not easily be identified. Moreover, failures appearing in one situation may be superseded by subsequent correct outcomes and, therefore, be hidden.We alleviate the above problems by making use of a special kind of situation, which we call checkpoints, such that the middleware will not activate the functions under test. We recommend testers to generate test cases that start at a checkpoint and end at another. Testers may identify relations that associate different execution sequences of a test case. They then check the results of each test case to detect any contravention of such relations. We illustrate our technique with an example that shows how hidden failures can be detected. We also report the experimentation carried out on an RFID-based location-sensing application on top of a context-sensitive middleware.

Experimental Study to Compare the Use of Metamorphic Testing and Assertion Checking

“…The oracle problem is not limited to the above kind of scenarios. For instance, for programs involving complex computations (such as partial differential equations [4], graphics-based software [5][6], database applications [7], large-scale components, web server, or operating systems [7]), their outputs are difficult to verify.…”

Algorithms for efficient symbolic detection of faults in context-aware applications

“…Validation of CAAAs has been the target of other researches [20,28,29]. However our approach differs from other techniques because it applies model checking to adaptation models, while other works focus on test case selection and runtime analysis.…”

Towards a Metamorphic Testing Methodology for Service-Oriented Software Applications

“…In general, x 1 is termed as the original test case, and y 1 is termed as the follow-up test case. We refer readers to [3][4][5][6]14] for more details about metamorphic testing.…”