Tests are failing on Jenkins
Tests are failing on Jenkins with error Please specify endpoints and restart your test. I have added endpoints in <con:service type="SOAP" name="xyz"> <con:endpoint authProfile="No Authorization">https://foo</con:endpoint> </con:service> Tests are running fine on my local machine606Views0likes2Comments
How to prevent ReadyAPI from randomly changing how it stores empty XML elements?
Why does ReadyAPI change how it stores a blank XML tag from, say <con:properties/> to <con:properties></con:properties> If I make one change and save, I may see many of these differences, which complicates review of the code. I see this in projects where Composite project is false, and in projects where it is true. The representation of blank XML elements is one of many things about how ReadyAPI stores a project that seem to change at random with each new version or sometimes randomly within the same version. I have tried setting the flag "Pretty prints project files", but this is not sufficient to stop this noise. Is there some other flag I can set so that the method for encoding the project doesn't obscure actual logic changes when I look at the differences? Preferably something that gets remembered in the project, rather than depending on a user setting? References: The following are a few postings that seem relevant, but don't clean up the random XML representations. "Version control - Diff is very confusing for ReadyAPI projects?" https://community.smartbear.com/t5/API-Functional-Security-Testing/Version-control-Diff-is-very-confusing-for-ReadyAPI-projects/m-p/209420#M47734 - Answer: Yes, currently, if you change one thing in ReadyAPI, several things in different places of the project might change as well. "How do I minimize merge conflicts in a ReadyApi composite project when working as part of a team?" https://community.smartbear.com/t5/API-Functional-Security-Testing/How-do-I-minimize-merge-conflicts-in-a-ReadyApi-composite/m-p/141151 - No accepted answer - Recommendation to check the flag "Pretty prints project files" "While this allows you to see exactly what has changed when diff-ing versions, it does have the problem that this is an application setting, thus you have to make sure all users set this value manually on their copies of ReadyAPI (If a user does not set this in their copy ReadyAPI it will revert to saving on a single line). Ideally I would like to see this as a project setting."Solved2KViews0likes7Comments
[Schema Compliance] Missing operation [XXX] in wsdl definition
Hi there, We have quite some functional tests running daily, that fail the schema compliance test with the error 'Missing operation [name-of-operation-here] in wsdl definition. Some test steps always fail on this step. When running the tests manually the test step pass, the entire test case frankly. The test step in question also check for soap faults as well as certain values in the responses and they always pass. I have refreshed the WSDL files and I can see the operations there. We are running Ready Api 3.6.0, what could be the issue? Thanks, Scarlet1.8KViews0likes5CommentsUI: How to minimize, close, or dismiss Assertions panel in ReadyAPI 3.6.0
The new version of ReadyAPI has a very different look and feel in some places. One change that I find very annoying is that SmartBear appear to have made the Assertions/Log panel for a request a fixed pane so that it is not obvious how to get it out of the way so that I have enough screen to view the request and response details. Does anyone know if there is an option somewhere to allow me to dismiss the panel in ReadyAPI 3.6.0?Solved1.9KViews0likes3Comments
how to stop exporting failed test cases result to a file in - FAIL.txt in afterStep
I have lots of pre steps in my test suite which might fail sometime but that is expected. But the problem here is this is generating a FAIL.txt file in Jenkins machine . is there any way to stop creating this file ? Thanks in Advance.866Views0likes3CommentsCalling a TestSuite from test step of another Test case
I have a requirement to call a Test suite from test step of another Testcases. Project structure Our Project structure is 1.TestSuite1 1.1 TestSuite1_Positive 1.2 TestSuite1_Negative 2. TestSuite2 2.1 TestSuite2_Positive. 2.2 TestSuite2_Negative 3. TestSuite3 3.1 Runner Requirement is to run TestSuite 1 from TestSuite3 --> Runner . Is there any way to achieve this ? Thanks in advance .Solved1.5KViews0likes4CommentsCustomising parallel runs
Hi Team , We are trying to figure out a way to run our test cases in a customised parallel fashion . To start with , we are using readyAPI paid version 3.2.5. Our Project structure is 1.TestSuite1 1.1 TestSuite1_Positive > 100 cases 1.2 TestSuite1_Negative > 20 cases 2. TestSuite2 2.1 TestSuite2_Positive. > 50 cases 2.2 TestSuite2_Negative > 30 cases 3. TestSuite3 3.1 TestSuite3_Positive > 50 cases 4. TestSuite4 4.1 TestSuite4_positive. > 10 cases test Suite 2 is dependent on TestSuite1 and it should run only after TestSuite1 is completed. TestSuite 4 is dependent on TestSuite3 and it should run only after TestSuite3 is completed TestSuite1 and TestSuite3 are independent and can run in parallel and TestSuite2 and TestSuite4 can run in parallel. What we are trying to achieve here to once we start our run , TestSuite1 and TestSuite3 should run in parallel. Once TestSuite1 complete its run TestSuite2 should start , similar for TestSuite3 and TestSuite4. Kindly help .Solved1.5KViews0likes4Comments
Previously working test no longer works...
Hi! I have been asked to run a ReadyAPI test that was last run about a year ago. I am now getting this groovy error when I try to run it: startup failed: Script3.groovy: 1: Unexpected input: '\' @ line 1, column 86. eDateFormat; use(TimeCategory)\u007B new ^ org.codehaus.groovy.syntax.SyntaxException: Unexpected input: '\' @ line 1, column 86. at org.apache.groovy.parser.antlr4.AstBuilder$1.syntaxError(AstBuilder.java:4597) at groovyjarjarantlr4.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:44) at groovyjarjarantlr4.v4.runtime.Parser.notifyErrorListeners(Parser.java:543) at groovyjarjarantlr4.v4.runtime.DefaultErrorStrategy.notifyErrorListeners(DefaultErrorStrategy.java:154) at org.apache.groovy.parser.antlr4.internal.DescriptiveErrorStrategy.reportInputMismatch(DescriptiveErrorStrategy.java:103) at org.apache.groovy.parser.antlr4.internal.DescriptiveErrorStrategy.recover(DescriptiveErrorStrategy.java:55) at org.apache.groovy.parser.antlr4.internal.DescriptiveErrorStrategy.recoverInline(DescriptiveErrorStrategy.java:68) at groovyjarjarantlr4.v4.runtime.Parser.match(Parser.java:213) at org.apache.groovy.parser.antlr4.GroovyParser.compilationUnit(GroovyParser.java:362) at org.apache.groovy.parser.antlr4.AstBuilder.buildCST(AstBuilder.java:405) at org.apache.groovy.parser.antlr4.AstBuilder.buildCST(AstBuilder.java:384) at org.apache.groovy.parser.antlr4.AstBuilder.buildAST(AstBuilder.java:424) at org.apache.groovy.parser.antlr4.Antlr4ParserPlugin.buildAST(Antlr4ParserPlugin.java:58) at org.codehaus.groovy.control.SourceUnit.buildAST(SourceUnit.java:257) at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133) at java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658) at org.codehaus.groovy.control.CompilationUnit.buildASTs(CompilationUnit.java:666) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:632) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:389) at groovy.lang.GroovyClassLoader.lambda$parseClass$3(GroovyClassLoader.java:332) at org.codehaus.groovy.runtime.memoize.StampedCommonCache.compute(StampedCommonCache.java:163) at org.codehaus.groovy.runtime.memoize.StampedCommonCache.getAndPut(StampedCommonCache.java:154) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:330) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:526) at groovy.lang.GroovyShell.parse(GroovyShell.java:538) at groovy.lang.GroovyShell.parse(GroovyShell.java:570) at groovy.lang.GroovyShell.parse(GroovyShell.java:565) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.recompileWithNewName(SoapUIGroovyScriptEngine.java:151) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.compile(SoapUIGroovyScriptEngine.java:142) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:91) at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:83) at com.eviware.soapui.model.propertyexpansion.resolvers.EvalPropertyResolver.doEval(EvalPropertyResolver.java:161) at com.eviware.soapui.model.propertyexpansion.resolvers.EvalPropertyResolver.resolveProperty(EvalPropertyResolver.java:149) at com.eviware.soapui.model.propertyexpansion.PropertyExpander.expand(PropertyExpander.java:213) at com.eviware.soapui.model.propertyexpansion.PropertyExpander.expand(PropertyExpander.java:221) at com.eviware.soapui.model.propertyexpansion.PropertyExpander.expand(PropertyExpander.java:156) at com.eviware.soapui.model.propertyexpansion.PropertyExpander.expand(PropertyExpander.java:152) at com.eviware.soapui.model.propertyexpansion.PropertyExpander.expandProperties(PropertyExpander.java:135) at com.eviware.soapui.impl.wsdl.submit.filters.PropertyExpansionRequestFilter.filterAbstractHttpRequest(PropertyExpansionRequestFilter.java:48) at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.filterRequest(AbstractRequestFilter.java:34) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.filterRequest(HttpClientRequestTransport.java:420) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:196) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:130) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) at java.base/java.lang.Thread.run(Thread.java:832) 1 error I get this error when it tries to evaluate this: ${=import groovy.time.TimeCategory; import java.text.SimpleDateFormat; use(TimeCategory)\u007B new SimpleDateFormat("yyyy/MM/dd").format(new Date("${#Project#birthDate0an}") - 58.year)\u007D} The code in question is put in a custom project property and birthDate0an exists and it is correctly initialized. Now as far as I can see the parsing of the groovy code fails at the "\u007B" (right curly bracket code in Unicode). Now I tried to replace "\u007B" by "{" and "\u007D" by "}" and it did not work so it looks like the inner curly brackets must be escaped. The only thing I can think could have changed between now and 1 year ago when that test was last run is the version of ReadyAPI. What can I do to make this test work again? Thank you and have a nice day! NickSolved2KViews0likes5Comments
Fixed API Testing vs Floating API Testing
May i ask you if we buy just Fixed API Testing for now and then if we want to buy API Performance and API Virtualization in the future, is that possible to add these licences to Ready API tool afterwards? And my second question is as you see below screenshot, ReadyAPI Custom Pricing have CI/CD Pipeline integrations speciality. So i wonder that could we decide the speciality of the licences according to our needs? I mean if we buy basic licences API Testing which is Fixed, is that possible add just CI/CD Pipeline integrations speciality to the Fixed license? If it is, could we learn its price, too.Solved1.2KViews0likes2Comments
Tests are failing on Jenkins
Tests are failing on Jenkins with error Please specify endpoints and restart your test. I have added endpoints in <con:service type="SOAP" name="xyz"> <con:endpoint authProfile="No Authorization">https://foo</con:endpoint> </con:service> Tests are running fine on my local machine[Schema Compliance] Missing operation [XXX] in wsdl definition
Hi there, We have quite some functional tests running daily, that fail the schema compliance test with the error 'Missing operation [name-of-operation-here] in wsdl definition. Some test steps always fail on this step. When running the tests manually the test step pass, the entire test case frankly. The test step in question also check for soap faults as well as certain values in the responses and they always pass. I have refreshed the WSDL files and I can see the operations there. We are running Ready Api 3.6.0, what could be the issue? Thanks, Scarlethow to stop exporting failed test cases result to a file in - FAIL.txt in afterStep
I have lots of pre steps in my test suite which might fail sometime but that is expected. But the problem here is this is generating a FAIL.txt file in Jenkins machine . is there any way to stop creating this file ? Thanks in Advance.
