Why model-based test automation is different and what you should know to get started

By: Contributor(s): Material type: ArticleArticleDescription: 1 archivo (598,7 KB)Subject(s): Summary: Test engineers, their managers, as well as the project developers often have many different views and misconceptions about tools and methods that provide test automation support. This paper compares model-based testing with three other generations of test automation. Model-based test automation can be considered a fourth generation test automation. It supports defect prevention, early requirement defect identification, and automatic generation of tests from models, which eliminates manual test design and reduces cost. However, to be effective at adopting model-based test automation, there are specific skills that will be required to incorporate this type of test automation into an organization. The paper discusses the organizational, personnel, and development lessons learned from working with numerous companies and projects over the past several years. It recommends how to get started, how to select a project, and how to organize a project. Finally, the paper describes how to measure, track and estimate the project completion date during the first non-pilot project.
Star ratings
    Average rating: 0.0 (0 votes)

Formato de archivo PDF.

Test engineers, their managers, as well as the project developers often have many different views and misconceptions about tools and methods that provide test automation support. This paper compares model-based testing with three other generations of test automation. Model-based test automation can be considered a fourth generation test automation. It supports defect prevention, early requirement defect identification, and automatic generation of tests from models, which eliminates manual test design and reduces cost. However, to be effective at adopting model-based test automation, there are specific skills that will be required to incorporate this type of test automation into an organization. The paper discusses the organizational, personnel, and development lessons learned from working with numerous companies and projects over the past several years. It recommends how to get started, how to select a project, and how to organize a project. Finally, the paper describes how to measure, track and estimate the project completion date during the first non-pilot project.

International Conference on Practical Software Quality and Testing, 2004.