CoreyVernon
AlumniJoined 4 years ago
User Profile
Alumni
User Widgets
Contributions
Re: how to run test suite for all environments one after another
Hello SanketSarode, One way to switch between environments is to include a setup or teardown script that calls the specific environment you want to move to. An example of that script would look like this: // Replace the project and environment names with those you need def proj = testRunner.testCase.project.workspace.getProjectByName("Sample Project") proj.setActiveEnvironment("Test Environment") To call the environment during runtime you can generate a command argument that calls the environment you want. The ReadyAPI documentation discusses this in further detail. I have provided a link below. https://support.smartbear.com/readyapi/docs/testing/environments/index.html I hope this helps. Corey658Views0likes0CommentsRe: Wait for TestComplete Step to end
Hello CristianE, I'm sorry you're running into this issue. I have found that it works more effectively to call your ReadyAPI project from TestComplete instead of the inverse. When you build your TestComplete test to prepare your environment, you can call the .xml file associated with your ReadyAPI project to execute the testcase. TestComplete will generate reports to the location of your choosing and include the API testresults in the test logs. Let me know if this suggestion is helpful. Corey907Views0likes1CommentRe: Git Integration Issue
Hello Dimitris, I'm sorry you're running into this issue. Are you making your .git commands through the ReadyAPI UI via the Git Console or are you utilizing the command line outside of ReadyAPI? Do you get the error when attempting both methods? I've provided the documentation below that walks through multiple methods of updating git repositories. https://support.smartbear.com/readyapi/docs/integrations/git/index.html Let me know if any of this helps. Corey1.4KViews0likes3CommentsRe: Connecting to Yugabyte Via JDBC
It seems that Yugabyte provides a JDBC driver based on Postgresql. This connection can be established in ReadyAPI by providing the connection string. I have provided links to the ReadyAPI documentation that walks through connecting to JDBC databases as well as the github repo for the Yugabyte Postgresql JDBC connection. https://support.smartbear.com/readyapi/docs/testing/data-driven/tutorials/jtds/jdbc.html?sbsearch=JDBC%20connection https://github.com/yugabyte/pgjdbc I hope this information helps guide you, Corey785Views0likes2CommentsRe: How to save data from the step "API Connection Test Step" kafka topic subscribe
Hi kol9mbla I'm glad to know that you're enjoying the API connection teststep. In addition to this teststep you can use the Datasink step to write data produced to any external source. Using these steps together should give you the desired outcome. I have provided a link to the documentation that explains the Datasink teststep. https://support.smartbear.com/readyapi/docs/functional/steps/data-sink.html?sbsearch=DataSink673Views1like0CommentsRe: GraphQL Project
Hi rammar In order to include your query parameter for your POST request, you would add this under the request body in a tab called "Query variables". Here you can include the parameters of your request. I have provided a link to the ReadyAPI documentation on GraphQL request. I hope this helps with your usecase. https://support.smartbear.com/readyapi/docs/requests/graphql.html1.2KViews0likes1CommentRe: ReadyAPI-Azure : how to increase timeout when running testcases in testrunner in azure pipeline
Hi pskitsme92 One possible solution to this timeout error could be to include a webhook. Webhooks do not wait for your request. Instead, they wait for a specific event on the server and send the request themselves. I have provided the ReadyAPI documentation on using webhooks. I hope this helps with your usecase. https://support.smartbear.com/readyapi/docs/testing/webhooks.html?sbsearch=timeout2.4KViews2likes0CommentsRe: JMS Endpoint is not editable
Hi arupacharya1784 I'm sorry you're having difficulty with JMS endpoints. ReadyAPI provides support for the TextMessage and BytesMessage objects (for outgoing messages) and for the TextMessage, BytesMessage and MapMessage objects (for incoming messages). I have provided a link to the documentation on JMS messaging that you may find useful when setting the endpoint. https://support.smartbear.com/readyapi/docs/testing/jms/message/about.html985Views1like0CommentsRe: Assertions not saved in Ready API 3.9.0
Hello, If you are using Git you may be interested in the Git Console that was recently added as a ReadyAPI update. This integration will let you make .git calls directly from the console after connecting to your remote repository. For more information on the Git Console please visit the link below. https://support.smartbear.com/readyapi/docs/integrations/git/console.html?sbsearch=Git1.6KViews2likes5CommentsRe: Can I put multiple project in one Git repository?
Yes. You can put multiple projects in one Git repository but they would need to be on different branches within that repo. The Git console in ReadyAPI gives you the ability to create or switch branches from the UI. More information on the Git integration can be found here in the documentation. https://support.smartbear.com/readyapi/docs/integrations/git/branches.html?sbsearch=create%20branch https://support.smartbear.com/readyapi/docs/integrations/git/index.html24KViews1like1Comment