... to do what? Just wondering what your thoughts were on the open2Test framework approach vs. using one of your existing frameworks.
I've downloaded the Open2Test docs and have poked through some of the code but haven't found sufficient time to compare its merits and shortcomings with those of the framework that I've been using for 5 years.
The problem is like many frameworks out there it is based on old ideas. There is nothing new in Open 2 Test in fact I found below par as far as frameworks go.
I currently work with a Hybrid framework that has 2 core assets. The Test Builder and an OR file. all the QTP script has is RunTest. QTP is only used for the OR build and the run engine. Both soon to be replaced with WATIN.
In the test builder testers select a window / frame if required the object the method for the object eg: click, set, get....
So the user builds the test and then via button copies those tests to a test sheet. In the QTP script Datatable we set the Excel with the test sheet and run the test.
The QTP script is interpreted at runtime and runs in memory. The results can be either run via QTP or QC or via a custom report engine.
It takes 10 minutes to teach a non automator to create effective automation with this framework.
You can use DP you can create and call custom functions and business processes.
As far as my experience with Open2Test framework is concerned it is based on the old framework approach Keyword driven but is more "disciplined"
I poked into their code a bit and most of it is a reusable stuff...all u need is a Global OR and start writing the scripts by pluggin in the library file - No configuration hassles
I reused their exception handling and reg exp code in my project. It supports DP, we can call our existing functions with a keyword, data driven, db testing is possible. Across the frameworks for diff technologies they has almost same keywords.
We are using it for an app which is .NET app embedded with browser controls and infragistic controls and our team customized this framework a bit and were able to make it work within 2 days. Business grps are also writing acceptance scripts without any knowledge on QTP and with very little training on keywords.
Wonderful part is, they recently released SAP framework and has big plans going forward, hitting different testing tools with the same approach. Recently information week magazine identified this initiative as innovative idea
Based on my 7 years of exp in automation, no solution is a "ready to work" one in real time.we have to think little away from our own great solutions and welcome new ones with much better constructive criticism esp for a opensource initiatives. Recommend you to post ur comments in their site and let them improve, I did the same.