QARun works well enough with DLLs, with the exception that it can't call DLL functions that require types other than strings, integers and pointers to integers.
I think the lack of support for user-defined types and Object Orientated Programming is a major shortcoming of the QARun scripting language. It hurts scalability and makes code difficult to organize. It frustrates me on a daily basis. It has basically forced me to take great lengths to do what would be common everyday stuff in other programming languages.
I haven't used any other testing software throughly, so I can't provide you with information about how much better or worse QARun is than another tool.
I think jbs was talking about calling other QARun scripts and creating libraries of QARun functions.
QARun supports both. Creating libraries of functions is a widely used practice in my company. There are a few negative things about it though. You have to be carful in the order that you include your libraries. And you can only include them once. There is not functionality to check if it's already included(IF def).
QARun can call other qarun scripts. You can share Public vars between them. Child scripts can also except parameters. There also other features that I can't recall right now, but you can check the QARun help.
"If your not part of the solution, there's good money to be made in prolonging the problem."
[This message has been edited by QAGUY (edited 03-04-2003).]
If your not part of the solution, there's good money to be made in prolonging the problem.
The Include statement in QARun is similar to the 'use' statement in Silk. I agree with QAGUY in that you really need to pay close attention to the order in which you place your include statements in a QARun script. QARun doesn't appear to have a multi-pass compiler which can insulate you from most of these problems. Another thing to consider is how much public domain code is available to handle the type of automation you are looking to create.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Another thing to consider is how much public domain code is available to handle the type of automation you are looking to create. <HR></BLOCKQUOTE>
James, could you elaborate on what you mean in the above statement. I don't think I understand.
Suppose you want to have some global variables and some functions that use that global variable. Better make sure that the complier sees the variable being declared before it sees a function trying to use that variable or you will get a compile error. Other tools compile in such a manner that it doesn't matter where you declare a variable because the compiler will look for variables before looking at functions. Feel free to drop me a line if you need more info than this.