| || |
Data driven testing - record or keyword approach?
I have been reading through some forum posts and also the QTP help files and am trying to decide the best approach for automating on a project.
We have the test data in spreadsheets which pretty much dictates a data driven approach - I can use the data to drive the tests and check for results, so that is a no brainer.
What I am not so sure of is whether to use a Recording approach or Keyword driven.
I am new to QTP and for now am the only full time person dedicated to automating. This will change next year and others will begin to take over maintaining the tests I have written. I am therefore thinking ahead in terms of maintainability and am trying to put some guidelines together now that other testers can follow.
I guess what would help is getting some of your experiences (good and bad) in order to help decide which is the best approach for the long term rather than just what will work now.
Re: Data driven testing - record or keyword approach?
That depend on the required usage of your automation.
If maintainability is what you want then avoid Record and playback.
just think in terms of
1. reusablity of function/Object
2. Extendability in terms of new Application/Module/Pages
3. Maintainability in terms of Object or flow change
4. Data segregation for future change
5. Driver integration with third party tools like QC , Excel, DB etc and Utility for them
6. Exception handling for Known and intermittent known Issues
7. Appropriate report generation
8. Sharing and versioning ( Change management) the work among team member ( may not required in your Case)
9. Traceability of all the Object, Lookup for functions etc so if in future change will easily identify the impacted area. So you need better plan and Automation Architecture.
I might missed few more points ... but you can start with by going thru with these terms , framework, descriptive programming , modular approach of automation , QTP Object Model , QTP with QC , Excel, databases, file system , WMI etc .