Tear down script not executed when project is executed from testEngine.
As part of our current project effort we have a teardown script that pulls out the runner data to pull out the execution data and push to a porta using a endpoint. We have come up with a groovy script library file that can do this activity. In our tearDown script we are trying to just invoke the function in the script library. This works fine with the desktop version of readyapi, but when the same project is executed through jenkins on testEngine the function or the tearDown script is not triggered. Could someone help out unnderstand what could be possible issues, and also suggest some resolution that helps us out. ThanksAbstractTestRunner 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-JodiRun ReadyAPI Projects in TestEngine
I have a groovy script that will be called in every test, placed the script within the repo under ScriptLibrary -> utils folder. Changed the Project Properties -> Script Library to the repo location ( $(System.DefaultWorkingDirectory)\repo name\ScriptLibrary\utils ) The scripts are imported and are running successfully locally but in the Azure pipeline the step where the script is imported it's throwing error. import utils.RetryUtils: org.codehaus.groovy.syntax.SyntaxException: unable to resolve class utils.RetryUtils Run ReadyAPI Projects in TestEngine - task: TestEngine@1 displayName: Run ReadyAPI project in TestEngine env: API_Key: $(SPARX.MIST.GCP.Dev.APIKey) inputs: filePath: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip testSuiteName: MIST_Refactor environment: Dev serverUrl: ****** serverUsername: *** serverPassword: ****** continueOnError: truejava.util.PropertyPermission" "*" "read,write error with executing tests from Test engine
I am using TestEngine to execute ReadyAPI tests. Seeing the below error when TestEngine executes groovyScript which accesses the testrunner. java.util.PropertyPermission" "*" "read,write Error. java.security.AccessControlException: access denied ("java.util.PropertyPermission" "*" "read,write") Same test run from local instance does not throw an error. Any help on what is the resolution for this issue?
21 Selenium startup error: on alertsite with chromebrowser
I am trying to build a selenium jar file on ubuntu wsl in an environment with chrome browser 85 using and I tried building it using java -jar command as mentioned in the document and it is working fine in my local environment. When I try to upload the JAR file built to alertsite via this code, it gives me error code 21 I did verify the main class is present in the jar file, and all the selenium libraries are installed as well. I presume its an issue due to the browser version mismatch on alertsite. Can someone let me know what the issue here is? which is the supported version on alertsite. Im not able to install older versions of chrome on my wsl as the official releases from google are removed. what can be done here? Thanks in advance PS: selenium version 3.141.59 and java version 11 i specify in my pom.xml during build. 21 Selenium startup error: on alertsite with chromebrowser
Issue with Mounting Network Drive in TestEngine
Hello SmartBear Community, I'm encountering an issue with running my ReadyAPI tests via TestEngine that involves mounting a network drive. While the same tests run successfully in ReadyAPI, they fail when executed through TestEngine. Even when the network drive is available in the machine, with Testengine I'm getting an error "FileNotFoundException" when trying to read files from it. But with ReadyApi my script works correctly. This is an example of script : import groovy.json.JsonSlurper import groovy.io.FileType import java.util.logging.Logger // Définition du chemin du dossier contenant les fichiers JSON def chemindudossier = "Y:\\Regression\\1_FADETS\\4_COMM\\communication\\" // Création d'un nouvel objet JsonSlurper pour lire les fichiers JSON def jsonSlurper = new JsonSlurper() // Initialisation de trois compteurs pour compter le nombre total d'éléments JSON, le nombre d'éléments qui ont la structure attendue, et le nombre de "Tué" def totalCount = 0 // Parcourir tous les fichiers JSON dans le répertoire new File(chemindudossier).eachFileRecurse (FileType.FILES) { file -> // Lire le contenu du fichier JSON def content = file.text // Parser le contenu du fichier JSON def data = jsonSlurper.parseText(content) // Vérifier que chaque élément a la structure attendue totalCount += data.size() } log.info("Le nombre de communication est : $totalCount") //message d'erreur si le totalCount=0 if (totalCount == 0) { log.severe("Erreur : Aucun lien entre personne physique et telephone n'a été trouvé.") } Based on the documentation of Testengine, I did understand that there is a groovy restrictions on reading/writing files. I tried this 2 solutions that they propose and didn't work : 1- Added -Dgroovy.allow.all=true in ReadyAPITestEngine.vmoptions file 2- Edited readyapi-testengine.bat to include the -Dgroovy.allow.all=true flag: "%JAVA%" %JAVA_OPTS% -Dgroovy.allow.all=true -cp "%CLASSPATH%" com.smartbear.ready.testserver.ReadyApiTestServerMain %* Could you please help me to find a solution to my problem? I'm really stack and cannot progress in my tests! Thanks!
Is it possible to integrate the Azure TestPlan Test cases and the ReadyAPI tests ?
I have created manual test cases in Azure devops Test Plan. I have automated the manual test case functionality using ReadyAPI. Now i want to link the Azure Test Plan test cases while running the ReadyAPI tests via the Azure pieplines. Is it possible to do so ? I am using the Azure devops extension named "ReadyAPI Test for Azure Devops" and "Publish Test Results" in my pipeline.TestEngine external JAR files - error - unable to resolve class
Background - We have test engine hosted on some linux server and we execute tests suing CURL cmd or POSTMAN. Given some external JARs When we add external JARs in /bin/ext folder of test engine server and re-start the test engine And run the tests using curl command from locally or using POSTMAN Then it throws error for groovy script test step saying unable to resolve class <className present in external JARs> on import statement itself. We have also configured .vmoptions of test engine server to read ext JARs but still it throws error. Locally, In ReadyAPI, we are placing those JARs in /bin/ext/ folder and it works perfectly fine. Any solution to this problem?How to use the External JAVA libraries with Test Engine hosted on Linux
We are using the Test Engine to run our Ready API test suites and this server is a Linux machine. We are referring the java library (com.jcraft.jsch.*) within groovy script and this is used for file upload. this works fine while running the test in local with the Ready API application but while the same test with Test Engine, this suites fails as Test Engine is not able to find the the reference of java library(refere below error). Can you help us with below questions * Is there a default location which the Test Engine looks for external library reference? * Is there a way to have our own custom path for external reference and let the Test Engine refer this path? We looked into the official documentation, it has the details of path for Ready API but not for Test Engine
