Please tell me the underlying criteria that is needed in creating an eValid script language?
Great question, thanks for asking ManuelV.
Here is a summary of the design principles that should answer your questions: http://e-valid.com/Products/Documentati ... iples.html
There are two considerations here:
First, the script language has to be readily parsible, like a programming language, so that it can handle test situations of any complexity.
So, there is relatively natural processing of strings and names and line continuation and all of that stuff.
Second, the language has to be simple to read and manipulate, because test scripts typically need to be changed a lot.
So, no arcane constructs here!
Hope this answers your question.
-- eValid Support