Radford
Frequent Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: Groovy assert using Datasource value always returns false when correct
Are you sure that the two values you are comparing in the assert are exactly the same? For example does one of the values have a trailing space? I'd log the two values as follows, just before the assert statement to check: log.info('expectedHTTPResponse = "' + expectedHTTPResponse + '"') log.info('ActualHTTPResponse = "' + ActualHTTPResponse + '"')2.6KViews0likes0CommentsRe: Disable Assertions using Setup script
What is the type of test step type are you trying to disable the schema compliance assertion on? because if it is a WSDL test step the class WsdlTestRequestStep has the method getAssertionByName. The following is a bit of code that is run from test case startup script that loops through all of the test steps and all of the assertions, and disabling all of the schema compliance assertions, hopefully this will give you some pointers. testCase.getTestSteps().each{testStepName, testStep -> // Only check the test step if it implements the assertable interface if (testStep in com.eviware.soapui.model.testsuite.Assertable){ testStep.getAssertionList().each{ testAssertion -> log.info('Test step "' + testStepName + '" Checking assertion "' + testAssertion.getName() +'"') if(testAssertion in com.eviware.soapui.impl.wsdl.teststeps.assertions.basic.SchemaComplianceAssertion){ log.info('"' + testAssertion.getName() + '" is a schema compliance assertion, disable it.') testAssertion.setDisabled(true) } } } }2.2KViews1like0CommentsRe: databaseConnectionContainer missing in groovy in readyapi?
I believe that I hit the same issue as you when I upgraded Ready API from 1.7 to version 2.8.2 (I'm not sure at what point the actual removal of the getDatabaseConnectionByName(java.lang.String) method happend). I switched my Groovy Script to use the GroovyUtilsPro object to get the JDBC connection, something like the following code: import com.eviware.soapui.support.GroovyUtilsPro def groovyUtilsPro = new GroovyUtilsPro(context) def jdbcConnection = groovyUtilsPro.getJdbcConnection('YourConnectionName') The GroovyUtilsPro object deals with working out if you are running in the environment mode or not and always returns the correct connection, which I also found very useful. (Full disclosure, I don't actually use the getJdbcConnection() method as I was actually only using the connection to get a Groovy Sql object, the GroovyUtilsPro actually also provides a getGroovySql() method)1.7KViews2likes2CommentsRe: How to get the test suite status in soapui using groovy script?
Hi Prabaharan, I think this is the link to my script that richie was talking about: https://community.smartbear.com/t5/SoapUI-Pro/How-to-get-response-error-from-run-Test-case-step/m-p/192775/highlight/true#M442233.8KViews1like2CommentsRe: How to get response error from run Test case step?
richie glad you found it useful. Just to mention in my "real world" testing scenarios, I actually put the script in a "TestRunListener.afterRun" event, that way I just have a single copy of the script that runs for all test cases (you can always add a filter to the event if you want to limit the number of tets cases it runs against).3.8KViews0likes0CommentsRe: How to get response error from run Test case step?
I'm not sure if this is what you are after, but I make extensive use of the "Run TestCase" test step. To help me debug, I always add the following to my "common" test cases tear down script: def logPrefix = testCase.getName() + ': ' log.info (logPrefix + 'Number of results = ' + testRunner.getResults().size().toString()) for(result in testRunner.getResults()){ if(result.getStatus().toString() != 'PASS' ){ def failedTestStepName = result.getTestStep().getName() def logPrefixStep = logPrefix.trim() + failedTestStepName + ': ' log.error(logPrefixStep + 'TestStep "' + failedTestStepName + '" finished with the status ' + result.getStatus().toString()) for(testProperty in testCase.getTestStepByName(failedTestStepName).getPropertyList()){ if(testProperty.isReadOnly()){ log.info(logPrefixStep + 'Output property: ' + testProperty.getName() + ' = ' + testProperty.getValue()) }else{ log.info(logPrefixStep + 'Input property: ' + testProperty.getName() + ' = ' + testProperty.getValue()) } } for(message in result.getMessages()){ log.error(logPrefixStep + 'Error message: ' + message) } } } Is this what you are after?3.9KViews4likes4CommentsRe: SOAPui 5.3.0 and API Ready 2.7.0 issues known?
While not a direct answer to your question, the latest release is 2.8.2, thus reviewing the list of bugs fixed: https://support.smartbear.com/readyapi/docs/general-info/version-history/bugs-fixed-in-ver-2-8.html should give you an idea of potential problems with version 2.71.6KViews2likes4CommentsRe: I want the data/ values comparison of a xml-file on my system with xml response of a rest API call?
As you have mentioned that you are looking for an alternative to Groovy, here is a suggestion (Note: This will only work if the file containing the XML data on your hard drive is identical): 1) First use a File Wait test step to pick up the file. 2) Run your REST request test step. 3) Within your REST request use a Message Content Assertion to compare the result of your API call with the contents of the file. The key thing to note here is that the file Wait test step provides the contents of the file as a variable "fileContents" (review the above linked doc page). This can be accessed from another test step via a property expansion, if you are unsure about these you can use the point and click Get Data functionality. If your XML file is not exactly identical (for example it contains todays date), then as nmrao mentioned you can use xmlunit, but this does involve installing 3rd party libraries and using Groovy, here's a link to a post I made previously about it: https://community.smartbear.com/t5/SoapUI-Pro/Groovy-XML-Comparison-Dynamic-XML-Attributes-are-not-ignored/m-p/140657/highlight/true#M316191.6KViews2likes1CommentRe: Is there a way to run the same groovy script before running every test case?
As mentioned above, events are the way to go, here is the Ready API documentation (The link above is for Test Complete, another SmartBear product): https://support.smartbear.com/readyapi/docs/testing/handling-events.html1.9KViews0likes1Comment