El-Jodi
Occasional Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
AbstractTestRunner error
Hi folks, since version 3.59.0 we are experiencing the following error message running our test via gilab within the rapi docker image: ERROR [AbstractTestRunner] Exception during Test Execution org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider com.sun.org.apache.xerces.internal.parsers.XIncludeAwareParserConfiguration could not be instantiated: java.lang.IllegalAccessException: class org.apache.xerces.parsers.ObjectFactory cannot access class com.sun.org.apache.xerces.internal.parsers.XIncludeAwareParserConfiguration (in module java.xml) because module java.xml does not export com.sun.org.apache.xerces.internal.parsers to unnamed module @2b62475a at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source) ~[xercesImpl-2.9.1.jar:?] at com.eviware.soapui.support.jdbc.JdbcUtils.createResultSetHolder(JdbcUtils.java:162) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcResponse.<init>(JdbcResponse.java:48) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.createResponse(JdbcSubmit.java:371) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.runQuery(JdbcSubmit.java:187) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.run(JdbcSubmit.java:158) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.<init>(JdbcSubmit.java:90) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.ProJdbcSubmit.<init>(ProJdbcSubmit.java:12) ~[ready-api-soapui-pro-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.panels.teststeps.ProJdbcRequest.submit(ProJdbcRequest.java:15) ~[ready-api-soapui-pro-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.run(JdbcRequestTestStep.java:238) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:311) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:56) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:192) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:117) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) ~[ready-api-soapui-3.59.0.jar:3.59.0] at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:142) [ready-api-soapui-3.59.0.jar:3.59.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:840) [?:?] running the same tests using the docker image with version 3.57.0 doesn't throw the error. Has anybody experienced something similar? Thanks for your support in advance. Regards El-JodiShow test suite name in gitlab tests reports
Hi community, we are using the readyapi testrunner via docker file in our gitlab ci/cd environment. In order to get a better view of the failled test runs, we edit the yaml using the command line parameters , so that the results not only show as lof file but also in the "tests" tab of the pipeline: unfortunately there seems to be no way to get the test suite name to be shown in the "suite" column does any body have an idea what could be missing in the yaml? variables: ..... COMMAND_LINE: " '-f./reports/' '-j' ./" run: .... stage: test script: - "/bin/sh -c $WORKING_FOLDER/EntryPoint.sh" artifacts: when: always reports: junit: reports/*.xml paths: - "./reports" expire_in: 1 week Thanks for your feedback in advance RegardsRe: readyapi Database connection
Hi kadir this is not an unusual behaviour, unfortunately. Probably has to do something with retrieving all the table information. I use the workarround of creating my DB query in a dedictaed DB tool (eg. DB visualizer or Squirrel or even an editor). When readyapi asks me if I want to build a query I press no and paste the query directly into the query window. Saves me a lot of time. Regards Holgergcloud authentification with service account
Hi community, we are trying to check our google storage buckets using ready api. For this we need a token to access the gcs. It works on my local machine inserting my personal token directly in the oauth token field but, as you might understand, I don't want this to be stored in any gitlab pipeline or log file. Has any body already gathered experience with connection rap to the google storage, and has come across a solution for automatic token generation?Re: How to excecute different environments in Gitlab CI/CD
Thanks for your answer nmrao, this would be a fixed setting for all test projects then, right? If that is the case it wouldn't help me, since I have a variety of test projects with different endpoints (services). Until now I'm using the workaround of creating a dedicated project for each endpoint in order to trigger them from our gitlab ci/cd pipeline. I was hoping to find a way where I integrate the two environments in one project and use some sort of configuration (eg. tags) within the project pipe line yaml. Cheers HolgerHow to excecute different environments in Gitlab CI/CD
Dear Community, I would like to know if it is possible to trigger specific environments from my readyapi test project via gitlab CI/CD. Our test projects are stored and executed in gitlab but I have not yet figured out how to run a specific environment within my test project (eg. environment1 runs against https://endpoint1.com and environment2 runs against https://endpoint2.com) Thanks for your answers in advance Regards HolgerRe: Kafka topic using OAuth2 authentication
Hi all, seems that I have just found somebody with an similar issue. We also use oauth2 for Kafka topics. But, although the advanced configuration detects the ttl of the token it doesn't automatically generate or refresh it. We have a similar setup as jfnumainville but had to implement a groovy script in order to have the token generated or refreshed. I had hoped that release 3.41.0 would bring a solution to this, since oauth2 was explicitly mentioned in the release notes, but it apparently didn't. As this issue is highlighted as solved, I would be interested in the solution. Regards all and happy testing Holger
