Model-Based Testing of SAP Modules

International audienceThis presentation provides an overview of how the model-based testing (MBT) process can help togenerate accurate test cases as well as executable test scripts for SAP R/3 module testing to auto-mate regression testing.In the MBT process, a model is used to capture the expected behaviour of the application under test,fulfilling the functional requirements. This model makes it possible to automatically generating testcases and test drivers including the traceability matrix between functional requirements to test cases.Linking requirements to the behaviour model implements the requirements-based testing (RBT)process and addresses two major issues: first, validating that the requirements are correct, complete,unambiguous, and logically consistent during modelling phase; and second, automatically generatinga necessary and sufficient (from a black box perspective) set of test cases from those requirementsto ensure that the design and code fully meet those requirements.In this talk, we show how tests can be automatically generated from a UML model to test the securityaspects of SAP Defense Modules. Defense Security Scenario Requirement Specifications have beenmodelled using UML 2. In our approach, the automatic generation of functional tests is based on anunambiguous UML model of the functional requirements of the application under test. This functionalmodel uses Class diagram, State machines and OCL expressions to represent the expected visiblebehaviours of the application, but it does not integrate the implementation details (it is not an archi-tectural representation). Requirements traceability is managed by tagging manually the effects of thetransitions in the UML model with the requirements. Then, this model ought to be sufficiently preciseto allow the generation of test cases (as sequences of operations) including expected outputs andthe traceability matrix between generated test cases and functional requirements. The testcases/expected output pairs are directly used during test case execution on the application undertest, to obtain an automated verdict (success or fail)