| || |
I know that there are many people out there who are "driving" there test cases using spreadsheets and keywords. My curiosity is in the kinds of keywords that are being used. Are most people on the level of creating business process specific keywords that allow a user to define a business process to undertake - i.e. "Login" - and then sending the name and password or are the approaches more on the generic level like "Enter Data - Name - Joe Blow - Password - getmein"?
Re: DDE approaches?
Well, I'm just getting started. For one test case, I have 3 scripts: Setup, Login, and Tests.
I've done this because I figured it would allow me to create another test case where I can run the same login and test scripts, with a different environment setup. Or, I could run the set with a different user login.
I am data driving my my test script, but much of that (so far, as I finish one level of complexity, I move on to the next), is just a list of values to enter.
I'm either going to have an environment table for scripts to access to know what to do, or incorporate them into an .ini file. The keywords would be application specific:
NoteType: Required, Optional, Activity.
Client: Yes, No
TSType: Basic, Hierarchy
NoteFormat: In-Line, Pop-up
That's off the top of my head. I'm getting close to "environment driving" my script.
"I can see my house from here!"
Jordan Gottlieb - Keeper of the QA Forums FAQ
Qualitech Solutions, Inc.
Senior Consultant, Orasi Software