Model-based testing
Model-based testing is an application of model-based design for designing and optionally also executing artifacts to perform software testing or system testing. Models can be used to represent the desired behavior of a system under test (SUT), or to represent testing strategies and a test environment. The picture on the right depicts the former approach. Because test suites are derived from models and not from source code, model-based testing is usually seen as one form of black-box testing. Model-based testing for complex software systems is still an evolving field.
- Comment
- enModel-based testing is an application of model-based design for designing and optionally also executing artifacts to perform software testing or system testing. Models can be used to represent the desired behavior of a system under test (SUT), or to represent testing strategies and a test environment. The picture on the right depicts the former approach. Because test suites are derived from models and not from source code, model-based testing is usually seen as one form of black-box testing. Model-based testing for complex software systems is still an evolving field.
- Depiction
- Has abstract
- enModel-based testing is an application of model-based design for designing and optionally also executing artifacts to perform software testing or system testing. Models can be used to represent the desired behavior of a system under test (SUT), or to represent testing strategies and a test environment. The picture on the right depicts the former approach. A model describing a SUT is usually an abstract, partial presentation of the SUT's desired behavior.Test cases derived from such a model are functional tests on the same level of abstraction as the model.These test cases are collectively known as an abstract test suite.An abstract test suite cannot be directly executed against an SUT because the suite is on the wrong level of abstraction.An executable test suite needs to be derived from a corresponding abstract test suite.The executable test suite can communicate directly with the system under test.This is achieved by mapping the abstract test cases to concrete test cases suitable for execution. In some model-based testing environments, models contain enough information to generate executable test suites directly.In others, elements in the abstract test suite must be mapped to specific statements or method calls in the software to create a . This is called solving the "mapping problem".In the case of online testing (see below), abstract test suites exist only conceptually but not as explicit artifacts. Tests can be derived from models in different ways. Because testing is usually experimental and based on heuristics,there is no known single best approach for test derivation.It is common to consolidate all test derivation related parameters into apackage that is often known as "test requirements", "test purpose" or even "use case(s)".This package can contain information about those parts of a model that should be focused on, or the conditions for finishing testing (test stopping criteria). Because test suites are derived from models and not from source code, model-based testing is usually seen as one form of black-box testing. Model-based testing for complex software systems is still an evolving field.
- Hypernym
- Application
- Is primary topic of
- Model-based testing
- Label
- enModel-based testing
- Link from a Wikipage to an external page
- www.omg.org/cgi-bin/doc%3Fformal/05-07-07.pdf
- www.methodsandtools.com/archive/archive.php%3Fid=102
- www.cambridge.org/us/catalogue/catalogue.asp%3Fisbn=9780521687614
- portal.acm.org/citation.cfm%3Fid=1370042%23
- web.archive.org/web/20120201171940/http:/www.cs.waikato.ac.nz/research/mbt/
- www.piketec.com/downloads/papers/Kraemer2008-Model_based_testing_of_automotive_systems.pdf
- robertvbinder.com/wp-content/uploads/rvb-pdf/arts/MBT-User-Survey.pdf
- www.springer.com/west/home/computer/programming%3FSGWID=4-40007-22-52081580-detailsPage=ppmmedia%7CaboutThisBook
- squall.sce.carleton.ca/pubs/tech_report/TR_SCE-10-04.pdf
- Link from a Wikipage to another Wikipage
- Abstract test suite
- Alloy (specification language)
- Black-box testing
- B-Method
- Boolean satisfiability problem
- Category:Software testing
- Concrete test suite
- Constraint programming
- Coq
- CRC Press
- Deterministic system (mathematics)
- Disjunctive normal form
- Domain-specific language
- Domain-specific modeling
- Equivalence classes
- Executable test suite
- File:Mbt-overview.png
- File:Mbt-process-example.png
- Finite state automaton
- Finite State Machine
- Gaussian elimination
- Markov chains
- Model-based design
- Model checking
- Model-driven architecture
- Model Driven Engineering
- Model-driven engineering
- Numerical analysis
- Object Management Group
- Object-oriented analysis and design
- Predicate (logic)
- Python (programming language)
- Software testing
- State transition system
- Symposium on Applied Computing
- SysML
- System testing
- System under test
- Theorem proving
- Time Partition Testing
- Unified Modeling Language
- Z notation
- SameAs
- m.04vb91
- Model-based testing
- Modellbasiertes Testen
- Modellbasiertes Testen
- Mudelipõhine testimine
- Prova basada en model
- Q1399743
- QXnB
- Teste baseado em modelo
- Тестирование на основе модели
- モデルベーステスト
- 基于模型的测试
- Subject
- Category:Software testing
- Thumbnail
- WasDerivedFrom
- Model-based testing?oldid=1102094874&ns=0
- WikiPageLength
- 15290
- Wikipage page ID
- 1343866
- Wikipage revision ID
- 1102094874
- WikiPageUsesTemplate
- Template:Cite book
- Template:Cite conference
- Template:Cite journal
- Template:ISBN
- Template:Reflist
- Template:Software testing
