1. Home
  2. Opkey Help
  3. 11. Model Based Testing with Opkey

11. Model Based Testing with Opkey


Model Based Testing (MBT) is an advanced feature of OpKey Web which allows Business Analysts to create a Model base design. It is a graphical view of test design representation which can be considered as a framework containing all the possible test scenarios. This model reflects the system behavior from a testing perspective and includes all scenarios, constraints, and dependencies that are relevant to testing.

Need of MBT?

Being a graphical view of representation of Test Designs, MBT is easy to understand, use and maintain. Model Based Test Design shows a complete Test Structure in which test script, test data and test cases works as backbone of the structure. The purpose of designing of the model based test is representing a complex test scenario in graphical view which is easy to understand for test users.

Getting started with Model Based Testing (MBT):

OpKey Web is now integrated with Model Based Testing feature, an advanced approach of software testing. Model based test design contains nodes of different shapes which works as building blocks of the MBT. User can easily drag and drop required nodes and connect their edges and vertices as per the test scenario. User can rearrange the added nodes and their connections. Each blocks should be connected with edges (connectors) from their vertices.

You need to create Function Library files and map them with corresponding blocks and their edges respectively. There may be multiple ways of connecting blocks, starting from Start Process & ending to Stop Process. You should ensure that every block is connected from its vertices through edges.

Once MBT models have been created and mapped with FLs successfully, you need to compile the MBT graph. There is an MBT Utility which can be downloaded from the Download link showing in the dropdown.

This utility must be running on your machine. Test Cases can be derived from MBT models in different ways. Further, you can generate the Test Cases for the edge/vertex or all coverage. The Test Cases generated in this way, denote the possible test scenarios. Once, Test Cases are created, you can view and analyze them. The Test Cases contain information about those parts of a model that should be focused on, or the conditions for finishing testing.



Was this article helpful to you? Yes 2 No