 Hexaware’s proven Automation Test Methodology has evolved from the Test Engineering Principles and the best practices observed and implemented by our team of talented and experienced Test Managers, Test Leads and Test Analysts. Our unique Hex Test Model has a built-in Test Project Management to improve the efficiency of the testing process.
Our Risk-Based Testing Approach forms the key to our methodology. Test cases for automation will be prioritized based on business risk and application complexity.
Hexaware Test Automation Framework covers the process of identifying recordable UAT test cases through all appropriate navigation flow of the application under test, creating reusable scripts, interpreting test results, and reporting to the development team using the Functional Test Tools and Test Management Tools.
The Test Case Driven Automation test approach will be followed with a combination of Linear, structured, shared and Keyword driven scripting techniques for viable Automation Testing.
The main concept behind this approach is to reduce all test cases to their most fundamental tasks. Test scripts will perform these tasks independently of one another. In this approach the entire functionality is keyword driven.
- Linear
Linear scripting approach is a simple record and playback method to automate a test flow / navigation of test cases
- Structured
Structured scripting use control structures for the scripts. These control structures controls the flow of the test script / test case using 4GL Language.
- Shared
During the process of testing, there may be certain actions which need to be performed repeatedly. This type of action is particularly useful for testing a function or method. By pulling out common code into reusable functions and methods, and sharing them will improve productivity and the maintainability of the test scripts.
- Keyword driven
The Keyword driven technique is used to create scripts in such a way so as to execute a particular test based on the keywords in the external data table rather than the code. The whole test set is driven by the Driver script and calls the corresponding intermediate level Script based on the keywords
The Test Automation team will focus on positive testing and will complement the manual testing process carried out on the Product/Application under Test.
Automated test results will be generated, formatted into reports and provided on a consistent basis for Test Reporting and management by integrating the functional and test management tool.
Pilot / Dry Run
The developed script will be executed. Successful scripts will be approved and made as read only. If the executed script is not successful, that script will be validated and if necessary, corrections/updates will be made and will be re-executed till the script is successfully executed.
Integrating Test Script with Silk Test Manager
Successful and approved scripts will be integrated with the Test Director for execution. The scripts will again be executed from the Test Director to verify if there are any integration errors. If there are errors the errors will be corrected and re-executed till the script is successfully executed. Deliverables from Hexaware:
- Traceability Matrix
- Automation Test Scripts
- Automation Regression Suite
Tried and Tested Best Practices of Test Automation
Automation testing reduces the test cycle calendar time and reduces manual resource time to run the tests. A reduction in test run time increases test development time. Increased test development time results in enhanced quality of the test coverage and early defect detection and correction. It also affords the ability to conduct more extensive testing by running a greater number of test cases, thus increasing the quality and reliability of the application.
Automated tests can be run repeatedly and consistently, leading to time saving as well as predictability. The benefits are even greater considering the fact that testing is run multiple times for debugging the tests themselves, testing the product/application, defect simulation of the defect multiple times to find the root cause, retesting to verify the defect fixes.
|
