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?194Views1like2CommentsIs 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.206Views1like1CommentDifference result between TestEngine and ReadyAPI
Hi Hi build my test with ready API, my test is OK, my test contains a groovy scripts however When I execute this test in TestEngine this same test is Failed. I add in this parametre : By default, Groovy scripting has limitations on writing data to properties and files. If you need fully functional Groovy scripts in your tests, you can turn off these restrictions. Turning off the restrictions can cause security vulnerabilities. To turn off the limitations, you need to set the groovy.allow.all system property to true. The way you do this depends on how you run TestEngine: but in my Test on TestEngine I have this error on my grouvy script., why the behaviour is different between TestEngine and ReadyAPI IDE ? Error. java.net.UnknownHostException: https Error. error at line: 201.1KViews1like4Comments