2004 · 58 citations · 10 references
Software MaintenanceTest EngineersEngineeringProject ManagementSoftware EngineeringModel-based TestingTest AutomationSystems EngineeringModel-based Software DevelopmentModeling And SimulationSystem TestingDesignSoftware DesignTest FrameworkTest ManagementSoftware TestingAutomationAutomated Test EquipmentTechnologyMechanical AutomationModel-based Test AutomationData Modeling
Test engineers, managers, and developers often hold differing views and misconceptions about test automation tools, and while model‑based testing is considered a fourth‑generation approach, effective adoption requires specific organizational and skill‑set capabilities. The study compares model‑based testing to three earlier generations of test automation and offers guidance on project selection and organization. The authors draw on lessons from multiple companies to outline organizational, personnel, and development practices, recommend project initiation and selection steps, and explain how to measure, track, and estimate completion dates for early non‑pilot projects. Model‑based test automation supports defect prevention, early requirement defect identification, and automatic test generation from models, thereby eliminating manual test design and reducing costs.
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.
10
Design for Testability—A Survey
Williams, Parker · IEEE Transactions on Computers · 1982 · 297 citations
Larry Apfelbaum, John R. Doyle · 1997 · 172 citations