Model-based testing is computer software proving in which test cases are derived in whole or in part from a model that describes some (usually operational) aspects of the system under test (SUT).
Universal model based on fit proving
The model is commonly an abstract, partial presentation of the organization test the desired behavior. The test cases gained from this example are functional tests on the same level of abstraction as a model. These test cases are collectively known as the abstract test suite. The abstract test suite cannot be made directly against the system under test as it is at the wrong level of generalization. Therefore, an executable test suite must be derived from the abstract test suite that can communicate with the system under test. This is done by assigning abstract test cases to concrete test cases suitable for execution. In the case of online testing (see below), the abstract test suite exists only as a concept but not as an explicit artifact.
There are many ways to "get" evidence of a model. Since the pilot tests and is usually based on advanced heuristics, there is no better way to do this. It is common to consolidate all related test shunt design decisions in a package that is often known as "test requirements", "purpose test" or even "use case". This package can contain e.g. information on the part of the model should be the focus for testing, or the conditions under which it is proper to stop the test (stopping test criteria).
Since test suites are derived from models rather than source code, based on the test model is generally seen as a form of black-box test. In some respects, this is not completely accurate. Model-based testing can be combined with the source code level test coverage measurement and functional models can be based on existing source code in the first place.
Model based on tests of complex software systems is still an evolving field.
0 comments:
Post a Comment