Hello Eswaran Mani,
WinRunner works as a command line interperter, whcih means that it runs the code and of course if these is an error it will report it... but in run time :-|. This is not really what you want to hear but this is how it works.
When you use compiled modules for example, like a script that has a sole purpose of holding funciton for your general use, this you "compile" by running it each time you make a change in the code.
Hope this helps...
Yes, I know nothing changed on this since these postings last year and WR still cannot do a syntax check on Main scripts ...
But it gets me quite angry if I start a big testset before I leave the office and when I come back next day I see that the 2nd test stopped because I forgot a bracket or something like that.
I'm seriously thinking about writing a little syntax checker for myself that checks things like brackets, semicolons at the end of statements, quotation marks for strings, ...
But writing this is not that easy as it looks like on the surface.
There are some editors that allow custom syntax (like UltraEdit, Crimson Editor). For these 2 editors a TSL syntax already exists, but I didn't find a possibility to do a real syntax check.
Does anybody know a good syntax checker (that can be modified to check TSL-syntax) or can give me a hint on that issue?