Forum Discussion
HP-Plano-TX-Soa
11 years agoOccasional Contributor
I can dispense with this work-around 'solution' if there is a way to get to the com.eviware.soapui.SoapUI.logMonitor object via any of the references that are already present in the soapUI TestCase teardown script context - there are four I know of - context, testRunner, testCase and log. Since I already have these Properties in my own customScripts Package of groovy classes, then I should try to use one of them to get to the desired logMonitor object if I can.
Is it possible to get to logMonitor via any of these four references? I would think this could be done either using the log or the testRunner reference, or maybe using the context reference. I'm not sure where to start to get the answer.
Is it possible to get to logMonitor via any of these four references? I would think this could be done either using the log or the testRunner reference, or maybe using the context reference. I'm not sure where to start to get the answer.
Related Content
- 5 years agohenil_shah
- 9 years agojeffgaer
Recent Discussions
- 8 days agoemoya