Forum Discussion
yes exactly that's the point: it's case sensitive and the name of the log file area has to be set exactly as it appears on the UI - unfortunately they use different versions all over the place:
SoapUI 5.4.0: "script log"
ReadyAPI 2.2.0: "Script log"
ReadyAPI 2.3.0: "Script Log"
:smileyfrustrated:
another interesting question regarding this topic is why the statement
"com.eviware.soapui.SoapUI.logMonitor.getLogArea( "..." )"
works if executed manually via UI but fails if executed automatically via maven plugin on the CI:
NullPointerException: Cannot invoke method getLogArea() on null object
another post mentioned the same already guessing that it only works in the environment with a UI present, but I am curious if we really have to live with that or if there's asolution to get this working in maven as well
The "Script Log" area only applies to the GUI and not the command line. But, you can use a content of the ReadyAPI log files which are located in the C:\Users\%username%\.readyapi\logs folder by default.
Related Content
- 3 years ago
Recent Discussions
- 19 days ago