Front-End Test Automation Practices – Model-based Hybrid Keyword/Data Driven Framework

Posted by Albert Gareev on Jun 04, 2009 | Categories: Practices

Original date: 30 Mar 2009, 1:30pm

Front-End Test Automation Practices – Model-based Hybrid Keyword/Data Driven Framework

1. Description
• Framework creation – Pure programmatically
• Test creation – scriptless, visual design
• Internal Data Model, capable to import/export data from various sources
• GUI/Database checkpoints, parameterized/transitioned
• Business Verification Rules
• Framework-based structure; capable to integrate external objects (e.g. MSXML DOM)
• Exception handling and recovery capabilities
• Test Case oriented execution (business logic outside of the code)
• Data-driven input and verification
• Extended business reporting
• AI-based validation methods

2. Advantages
• High usability and re-usability, maintenance doesn’t require coding
• Compact code and scalable architecture
• Test Plan / Test Scenario creation doesn’t require programming or training on the Testing Tool
• Extensive test flow coverage
• Multi-application support
• Data and code are separate
• Reproducible and proven test results, convenient and transferable Test Reports
• Built-in Consistency and Severity Validation

3. Disadvantages
• Requires initial investment for design and implementation of the Framework

4. Applicability
• Comprehensive Functional Testing for multi-application, multi-platform products, featuring huge number of complicated Test Cases
• Smoke-Regression-Sanity Testing Cycle with extensive coverage and validation
• Test Plan / Test Scenario execution (Batch run)
• Big and changeable data set and data transitioning cases
• Excellent support of distributed teams
• Integration with other testing tools
• Mid- and long-term automation goals

Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.