Forum Discussion
Hi Rao,
Thank you for your reply again. Here is another example of how unhelpful I find the messages in the logs. In the SoapUI log I have this error:
So I do as it states and look in the error log for the details. That shows this:
There are no additional details. I don't have any idea what Script1 is as I have many scripts - why doesn't it refer to the script by the name I have given it? There is no line number anywhere, which would at least help. The variable it is complaining about *was* one I was using but I now no longer use it. I have searched every script individually for the variable in case I have a bad reference but the search string is not found in any script. Saying 'see error log for details' would be really helpful *if* there were some actual details rather than a repeat of what is in the SoapUI log. Do you understand the difficulties this is now presenting me with?
I will take a look at Ready API as I'm disheartened with how hard simple debugging is in SoapUI Pro. It is costing me huge amounts of time to track down errors. I really don't want to have to switch products though.
Thanks.
Gary.
Not sure how tests are run in your case.
See the attached screen shot, it shows the line number where the problem is clearly. And it always varies the script name irrespective of the groovy script test step name i.e., error always shows Script<xxx>.groovy and is the intended behaviour. I ran the groovy script test step from SoapUI Pro. And wonder how did not show for you?
And you dont have to be dishartened. You can post the problems in the active community or take it up with support.
- nmrao11 years agoCommunity HeroIf you run one more time, it may show up as Script3 and so on.
- GMSoapUI11 years agoContributor
Hi thanks for the replies.
I have *never* received an error message like yours where it clearly shows the line number responsible for the error. I've been using SoapUI Pro since around September 2014.
I run my tests via a Groovy script. The main script runs on a loop that is on a timer of one hour. Each time that script executes it calls a driver script that runs all the test steps in turn for each test case. It is automated. Even running the scripts manually I never get a line number for the errors and never have done. It's really frustrating.
Regards
G
- nmrao11 years agoCommunity HeroHmm. May you want to try the same example that was shown in the screen shot to see atleast that shows same error as above?