Getting started down the right path: Test Automation Framework
User Greg Minamide (Greg.Minamide@ImageX.com) posted:
I recently introduced the idea of a Test Automation Framework to our
Engineering Group here (Dev, SQA, IT, PM, etc.). Feedback was great! (BTW,
we've been using procedural style scripts due to time constraints with all
projects) I've been encouraged and supported to create this test automation
framework. Documentation out there on the internet from Carl Nagle and
others has been great.
The Project Management team has supported the framework idea, but since I'm
the only one who has a desire to learn automation tools, I'll be pretty much
the only one working on the framework. Which means that other new test
automation must be created while the framework is being worked on.
Does anyone have any suggestions as to how to get started in some
incremental fashion with the framework? I'd like to continue to generate new
scripts and maintain current scripts while working on the framework. I'd
like to use and integrate any newer scripts into the framework (eventually).
I'm also rather stumped as to how to start such a massive undertaking, so an
incremental approach might work out best.
10210 NE Points Drive, Suite 200
Kirkland, WA 98033
Direct (425) 576-6617
Fax: (425) 576-6668
Main: (425) 576-6500
Toll Free: (877) 682-0880
This communication may contain privileged or other confidential
information. If you are not the intended recipient, or believe that you
have received this communication in error, please do not print, copy,
retransmit, disseminate, or otherwise use the information. Also, please
indicate to the sender that you have received this email in error, and
delete the copy you received. Thank you.
Re: Getting started down the right path: Test Automation Framework
User Carl Nagle (Carl.Nagle@sas.com) posted:
My first suggestion would be to not go out and "create" your own framework from scratch if you don't have to. Use the tools and code already made available whenever possible. That is the intention and purpose of the Data Driven Engine and associated tools made available to everyone via the RobotDDEUsers user group.
This not only provides a ready test automation framework but it provides the forum by which you can gain support and also contribute to the evolution of the framework. You are not locked in to the features available. Features are often added by individual users (and you, too) and distributed among all users.
Anyway, this automation framework--the DDE--allows you to integrate existing scripts and data driven testing and perform any conversion from one to the other as your needs require or as time becomes available.
Although I think you have seen this, it is often worth repeating: http://groups.yahoo.com/group/RobotDDEUsers
If at all possible, don't try to create a framework from scratch while also being responsible for ongoing test automation. Both will likely suffer.