I worked on different automation tools in different companies. But the present company I am working for is a little different. For Scripting you have to use Programming language, they don't allow you to record anything, They don't allow to use Usercheck, Bitmap Check, cannot use csv.file, cannot use Goto statement, cannot use While loop, cannot use Windows Check, Cannot use Form Check and many many don't and do's. Even you put an alias name, they may call it as poor conventional name. Does anybody have such a nice environmental experience would like to share ??
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by QA_Accent: Does anybody have such a nice environmental experience would like to share ?? <HR></BLOCKQUOTE>
While we do not have as rigid a structure as you suggest, I would appreciate a copy of these guidelines if possible?
Have you figured out the reasoning behind these does and don'ts? The project I am working on requires a lot of evidence of function being verified and we have rules, but nothing to the extent of making the tool useless.
Some ideas on how to get by in for the use of these types of functionality provided by the tool:
1. figure out why they feel the way they do 2. educate the purpose of these functionalities
3. give demos on how to use them and how they can save an enormous amount of time
Please add to this list as I am interested in peoplese ideas to get buy in.