Giri Prasad Palanivel, an automation testing engineer for aspire systems, shared their successful automated testing experience:
Rapid test automation using testcomplete
Http://www.automatedqa.com/blogs/post/11-02-28/rapid-test-automation-using-testcomplete/
Some excerpts are as follows:
About the Framework Design:
Keep in mind that a framework that worked for one particle project may not be a good fit in another project. So let me list few points to consider while designing your framework.
- Separate your data from your tests.
- Build a library of common functions to aid in code reuse.
- Have test data/expected data in a format which is widely supported in and out of the selected automation tool selected.
- Try to have the framework independent of the tool/language.
- Accommodate Exception Handling and recovery scenarios.
Modify the recording script:
Once you 've finished recording, go back to your recorded scripts and examine the code. Look for places where you can modify it per your framework design. Ask questions like:
- Which part of the code can be reused/modularized/parameterized?
- How to best organize your code guest SS suite/project/modules?
- How tested objects are to be stored in 'namemapping'
- Decide 'testedapps' launch properties.
Object Recognition:
We might come into ss a few objects which are not readily recognized. In that case we may need to consider the following workarounds:
- Try for a regular expression/wildcards in properties to identify the object.
- Have a combination of properties of an object/control to identify it uniquely.
- Relatively identify the objects-as parent, child and positional constraints etc.
Author's blog:
Http://automate101.wordpress.com/