How to build SQL query using strings whose value should be retrieved from TestCase property
Suppose i have the following properties defined in the Test Case Properties FromTime =2023-11-15 23:00:00 ToTime =2023-11-16 23:00:00 I want to replace the time given in the below query with the above test case property variables. How to do that in ReadyAPI JDBC datasource ? SELECT * FROM Table1 where TagId = 4314 and Time > '2023-11-15 23:00:00' and Time < '2023-11-16 23:00:00' I am able to retrieve integer values like TagId and use it by adding 'Prepared Properties' within the JDBC datasource window. But if i add the string and use it inside the query, data is not fetched as the string is not interpreted properly.362Views1like7CommentsIs 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.205Views1like1CommentHow are you securing secrets for storing your projects in github?
We're trying to migrate our ReadyAPI suites into github and I'm getting a little stuck with ReadyAPI's documentation on how to encrypt passwords we use to test our application, I'm hoping someone has a simple answer they can share. Our application passwords are stored in auth manager or request properties, when this project is converted to a composite project and pushed into github those values are visible so I have followed documentation to try and mask them without success. 1. Encrypt the project - this stops the project being a composite project so we're back to single use for upgrades and preventing people from making changes and keeping them in a branch. Doesn't seem like this fits. 2. Password protect the project - doesn't obsfucate the passwords anywhere. 3. Move the passwords to encrypted properties - Feels very hacky and clunky, makes the auth manager redundant and isn't very user friedly. I haven't been able to find any other in application solutions other than the above, I was looking at keystores/ truststores but neither seem to fit the requirement. This has left us with the only option we can see which is to write a groovyscript to pull the passwords out of an encrypted keepass kdbx file to use at runtime. This is not my preferred approach as I would rather use in built features with ReadyAPI support documentation... If anyone knows of other things to attempt or can share how they managed it in their project that would be appreciated.Solved610Views1like4Comments3.44 issue with java.net.SocketTimeoutException: Read timed out
test step is failing due to "java.net.SocketTimeoutException: Read timed out", we tried increasing the socket timeout but it is still failing after the default 1 minute time. this project and test step is working fine when using 3.41 readyapi version but same test is failing in 3.44 and the latest 3.45 versions. please let us know what need to be done here as this impacting our regression testsSolved1.3KViews1like2CommentsReadyAPI and Jira integration
Hi, I am trying to integrate ReadyAPI version 43.1 and JIRA plugin version 1.6.4 instance so we can push issues from ReadyAPI to JIRA with the hope of creating better traceability. However, when I select the JIRA button at the top of the toolbar, JIRA opens, I select the project and issue type, then select ok.Nothing happens after that. What am I missing here? I was expecting a form to open within ReadyAPI so I can begin to enter details on the issue. Followed this link for set up:https://github.com/SmartBear/ready-jira-plugin/wiki/Creating-JIRA-Items Please find attached images for ReadyAPI logs.323Views1like1CommentHow to configure gitlab pipeline for ReadyAPI from TestRunner
We are trying to configure gitlab pipeline for ReadyAPI from TestRunner commandline , We have added below code into the ".gitlab-ci.yml" file in gitLab ------------------------------- stages: - build - test build: stage: build script: - echo "Building Pipeline" test: stage: test script: - echo "Testing Pipeline" - chmod +x "PATH TO testrunner.bat" -a "-f PATH TO \Test Reports" "-RProject Report" -FPDF -E PATH TO PROJECT FILE --------------------------------- The code is commited to GitLab. When i run the Pipeline the execution is failed due to below Reason: -------------------------------------- chmod: invalid option -- a BusyBox v1.32.0 (2020-11-23 21:18:59 UTC) multi-call binary. Usage: chmod [-Rcvf] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse -c List changed files -v List all files -f Hide errors ERROR: Job failed: exit code 1 ------------------------------ Could anyone please provide the solution for this. Vallalarasu_P1.3KViews1like5CommentsHow to handle when there is a separate Basic Auth endpoint and api endpoint for each environment
How to handle when there is a separate Basic Auth endpoint that returns a JWT and api endpoint for each environment Here is the use case: 1. There are multiple environments and each environment has a tenant. Example <env1><tenant1>, <env1><tenant2>, env2><tenant1> 2. Each environment has an auth endpoint and api endpoint. Example: Auth endpoint: https://<env1><tenant1>auth.com API endponts: https://<env1><tenant1>api.com/api 3. The auth endpoint is Basic Authentication and requires a username with this structure: username: <env1><tenant1>/username password: *********** 4. The auth endpoint returns a JWT token, in the following response { "access_token":"JWT", "profile_id":"", "token_type":"Bearer", "expires_in":86400 } 5. The access_token must be parsed from the response and then included in the Header of the api requests. In it's simplest form, I was able to accomplish this by using: - No Environment - Hardcoding the Auth endpoint - Hardcoding the api endpoint - Getting the token in an auth request 'Login' test step - Grabbing the token and using it in the next step by placing this in the header: Bearer ${Login#Response#$['access_token']} But I need to be able to automate this so that I can switch environments at run time. I've done a lot of research and haven't found many suggestions besides 'create a script'. I'm hoping there are other ways, but if I have to go the script route, it's not the end of the world. Has anyone else encountered a similar scenario? What is the easier strategy for handling a scenario like this? I appreciate any advice! NOTE: I can't seem to use the built in Authentication Manger in ReadyAPI because the Basic Authentication returns a response that must be parsed. Unless there is a way around this that I don't know about 🙂Solved2KViews1like10Comments