ReadyAPI-Azure : how to increase timeout when running testcases in testrunner in azure pipeline
I have been running some test cases in ReadyAPI windows application and increase the timeout for the testcases so they runs OK, but when running with the testrunner-commandline in Azure pipeline, some of the test cases times out. These test calls Selenide (Selenium) teststeps, where we have implemented some automated GUI test and they take a longtime to execute. Is there an options for the testrunner - test cases timeout, there is a testrunner bat file but does not include an obvious testcase-timeout option.Solved2.4KViews0likes7CommentsDifference 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.1KViews1like4CommentsLicense file installation in Docker
I am trying to install TestEngine with Dockerfile. Into a K8S Cluster. I have simply this in my Dockerfile. FROMsmartbear/readyapi-testengine:latest But, I am seeing error 16:20:41,864 ERROR [QuartzJobsScheduler] Missing License Details, scheduleLicenseExpirationJob would be skipped 16:20:41,864 ERROR [QuartzJobsScheduler] Missing License Details, scheduleLicenseTokenUpdateJob would be skipped All, I want to know is where to install the license file in the Dockerfile. I HAVE the license file .key file with me. not on the license server. I tried copying the file to the / in the Dockerfile. Like this: COPYabcd.key/abcd.key But that didn't help. So, please I am looking for the path where the license file need to be placeSolved1.1KViews0likes1CommentReadyAPI TestEngine proxy bypass?
Hi all, With the recent release of TestEngine 1.26.0 it now supports using a proxy server. This is really helpful because I can now use the API to install (and uninstall) the license used by TestEngine. However it seems all the traffic from the tests being run in TestEngine also defaults to using the proxy - which is not so helpful for tests of internal systems that can not be accessed via the proxy. So what I'm looking for is a way to add exceptions to the proxy server? Since the the proxy is configured in the 'ReadyAPITestEngine.vmoptions' files I tried adding "-Dhttp.nonProxyHosts=mycompanys.domain.com". But doesn't seem to change TestEngine's behavior. Does anyone have any ideas of how to encourage TestEngine to not use the proxy when running tests (but still leave it there for adding and removing the license)? (in a similar way to just turning the proxy off from the button in ReadyAPI) Thanks EddieSolved1KViews0likes1CommentGetting results when using TestEngine as a container? ...
We use ReadyAPI stand-alone, and are going down the path of using TestEngine to run tests as part of our CI/CD pipeline. I see that TestEngine when running continuously has a web interface where I think you can see results. But how is this handled when using it as a container that instantiates when needed and then goes-away when the tests are complete? How do you see results? Thanks very much in advance.Solved1KViews0likes3CommentsLicense is not installed or has expired
We have users that are connecting to our ReadyAPI TestEngine server that get this this error every couple of days, Error, ReadyAPI TestEngine license is not installed or has expired. This is corrected each time by reclaiming the license, but it is holding up work until it is corrected. Our license does not expire until June. Has anyone seen experienced this and found a fix?Solved991Views0likes1CommentHow to reuse a groovy teststep inside the project assertion scripts
I have a working groovy test script (a helper Cookie class with instance creation inside the script): context.setProperty("Cookie", new Cookie(log, context, testRunner)) and re-using the Cookie: project = testRunner.testCase.testSuite.project; testStep = project.testSuites["Helpers"].testCases["Objects"].testSteps["Cookie"]; testStep.run(testRunner, context); log.info context.Cookie.info() Runs fine from other groovy scripts in the project. But I need to re-use the code in the assertion scripts as well. Tried import com.eviware.soapui.support.types.StringToObjectMap import com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner //def Runner = new WsdlTestCaseRunner(messageExchange.modelItem.testStep.testCase, new StringToObjectMap()); def Runner = new com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner( messageExchange.modelItem.testStep.testCase, new com.eviware.soapui.support.types.StringToObjectMap()); def mySteps= messageExchange.modelItem.testStep.testCase.testSuite.project.testSuites["Helpers"].testCases["Objects"].testSteps["Cookie"]; mySteps.run(Runner,context); log.info mySteps.name log.info context.Cookie.info() but got name is ok; Runner is a valid instance. But Cookie is null. Error in assertion script of the [Login - Unregistered Mobile User Login] test step: Cannot invoke method info() on null object Can anyone help me solve the problem, please... Script library works fine but is not an appropriate case as it requires additional permissions to write to the destination folder - a jenkins job on a cluster...Solved983Views0likes1CommentPermission issue in Test Engine
I am trying to run Ready api tests in Test Engine. C:\Program Files\SmartBear\ReadyAPITestEngine\bin>ReadyAPITestEngine.exe got started from Terminal successfullyon remote desktop. When I am running test jobs on Jenkins I am getting below error: 21:55:00,269 INFO [org.eclipse.jetty.server.RequestLog] 10.163.195.160 - - [01/Aug/2022:21:55:00 +0000] "POST /api/v1/testjobs HTTP/1.1" 400 75 "-" "Jersey/2.32 (HttpUrlConnection 11.0.14)" 94 21:55:00,442 INFO [com.smartbear.ready.testserver.server.ReadyApiTestServerSecurityPolicy] Permission denied: ("java.io.FilePermission" "C:\Users\prajvaidya\AppData\Local\Temp\ts_project_aa50ef98-067c-49b8-a9ef-bf730d7eb486\.git\refs\remotes" "write") I checked I have all the permission on remote desktop and to the above folder as well.943Views0likes3CommentsWait for TestComplete Step to end
Hello, I recently started using ReadyAPI and I have a question about TestComplete Step I added a TestComplete step to my ReadyAPI Test Case to prepare the environment for the next steps (restore database, run some SQL scripts etc) and I observed that ReadyAPI doesn't wait for TC test to end, but immediately moves on to the next step. Is there a solution to wait for TestCase to be passed before moving on ? Edit: Also, I observed that even if I have the "Automatically displays test results after the test run is over" unchecked, TestExecute will automatically open the test result (.mht) file at the end of execution. TestExecute and TestComplete versions: 14.81.217 ReadyAPI version: 3.30.0 Regards, CristianSolved903Views0likes3CommentsTestEngine & Pre-encoded endpoints ReadyAPI 's preferences
Hi I have implemented ReadyApi's test run with our integration tests Azure DevOps, I can run the tests in the pipeline without any issues... I just have a small issue with our tests, for this to work I need to set up preferences in ReadyApi to run HttpRequest. The Pre-encoded endpoints box needs to be checked. Are these preferences that can be set on TestEngine as these preferences do not depend on the ReadyApi XML files in our project? thanks899Views0likes2Comments