| || |
Test Frame Design. (long)
User oleg8888 (email@example.com) posted:
New Boss - New rules.
Automation Geniuses, I need your help.
Here is the automation structure we currently using.
Application - web based Resource & Project managing tool.
Test Tool - Data driven (Excel) engine. Spreadsheets are being
created by QA engineers who don't touch the code ever.
All test data is being stored in Excel, however, there are common
procedures that had to be coded with TSL. For example:
Creating a new project, assigning a position to it......
I can call this function (CreateProject) from the Excel using a
string with parameters...
We have a number of similar functions (we call them modules) and the
need for them is growing rapidly. It takes me no more then a day to
code one of this modules and we've been using them for quite a while
If there is a change in an application, it takes minutes to update
the module and we don't have to touch the test data.
Now, the new manager, who came from development and has no knowledge
of QA less of automation wants to do something different.
He wants to move the modules out of the TSL and put them in to Excel,
so each engineer can create modules of their own.
I am afraid I will end up c4eating another automation tool on top of
I will have to input logics in Excel (if, else, while...) and I think
it'll be more complicated.\
What do you guys, think?
Any feedback is highly appreciated.
Re: Test Frame Design. (long)
User Decker, Jay (Jay.Decker@nordstrom.com.nospam) posted:
This sounds exactly like what I am implementing here. I am interested to see how you decide to implement your looping