Posts Tagged ‘Test Automation’
Testcomplete™ can be used to automate testing of Web & windows applications. Although TestComplete™ supports major standard controls, windows and objects in a wide variety of applications, there are some controls and windows that cannot be recognized by Test Complete directly. For example cells in few grid controls, buttons in some flash applications may not be accessible by TestComplete™. Handling TestComplete™ during such conditions makes automation little challenging.
It is possible to overcome these kinds of difficulties by using a low-level recording approach to test such applications. The main drawback of such an approach is that the script will require several changes even for a simple UI change in the application. So, creating and maintaining a stable script with this method is also not possible. Low-level Recording will be usually used in TestComplete™ for automating Testing in browsers other than IE and Firefox. Any application that needs to be tested in other browsers (such as Google Chrome or Opera) using TestComplete™ automation needs to approach low level recording technique.
In Test Automation, Data driven frame work is a most effective frame work which gives more test coverage, with less effort.
It becomes necessary for testing an application with different test data even in automation testing. While developing test automation for these types of application, Data-Driven frame work is best to use.
General Approach for creating data driven test:
- Record (or develop) your test scenario with a set of test data in your tool.
- Create data storage (Excel, csv or data base) and in which give multiple values for each test data.
- Replace the values in the recorded script with proper variables.
- Write script to access a set of test data from the storage, and assign it to those variables. While executing the test these values will be used.
Test automation is not about removing testers but to make use of their time better. It is impossible to automate testing completely, and it has to be a mix of automation and manual testing. If you have decided to automate testing, below are some practical tips for implementing any test automation initiative:
1. Focus on the methodology and not the tool
A clearly defined automation methodology that covers how the automation process will be conducted can eliminate most of the frustrations associated with automation by providing stakeholders with an upfront understanding. This would provide a fair idea on what is needed to automate tests, which includes tool selection as well as the rest of the automation process.
2. Choose tools that are scalable to meet future needs
- Test automation is expensive and takes ages to justify the investments.
- Automation resources are top-heavy and would mean a lot of upfront costs.
- Product roadmap is not clearly defined and we aren’t sure if automation is appropriate for us?
These are some of the initial reactions that we get to hear whenever we think of test automation. These reactions aren’t unfounded and it merits careful assessment.
Some questions to consider before deciding to automate are:
- Is your product fairly stable and do you have paying customers for its initial version?
- Does the product have a clearly defined roadmap?
- Does every version upgrade, both minor and major warrant running all the functional tests over and over again? Essentially, the test scripts would be re-used multiple times justifying the investments