Editing Model-based testing (section)

==Deploying model-based testing==
[[File:Mbt-process-example.png|right|frame|An example of a model-based testing workflow (offline test case generation). IXIT refers to ''implementation extra information'' and refers to information needed to convert an abstract test suite into an executable one. Typically, IXIT contains information on the test harness, data mappings and SUT configuration.]]
There are various known ways to deploy model-based testing, which include '''online testing''', '''offline generation of executable tests''', and '''offline generation of manually deployable tests'''.<ref name="pmbt">[http://www.cs.waikato.ac.nz/research/mbt/ ''Practical Model-Based Testing: A Tools Approach''] {{webarchive|url=https://web.archive.org/web/20120825215944/http://www.cs.waikato.ac.nz/research/mbt/ |date=2012-08-25 }}, Mark Utting and Bruno Legeard, {{ISBN|978-0-12-372501-1}}, Morgan-Kaufmann 2007</ref>

Online testing means that a model-based testing tool connects directly to an SUT and tests it dynamically.

Offline generation of executable tests means that a model-based testing tool generates test cases as computer-readable assets that can be later run automatically; for example, a collection of [[Python (programming language)|Python]] classes that embodies the generated testing logic.

Offline generation of manually deployable tests means that a model-based testing tool generates test cases as human-readable assets that can later assist in manual testing; for instance, a PDF document in a human language describing the generated test steps.