Contributions
GraphQl request : extra quotes added to the Query Variables when the Query Variables is a property
Same question that was already asked couple of years ago and didn't get an answer: When I'm populating Query Variables for GraphQL request using a saved as a property JSON object, it is sent with double quotes around it when it expected to be just a JSON object. Query Variables: ${Properties#addBpVariables} addBpVariables saved in the Properties: {"billingProducts":[{xxxxxxxxxxxxxxx}]} Query Variables processing values: "variables":"{"billingProducts":[{xxxxxxxxxxxxxxx}]}" As a result I'm getting back HTTP 400. If I post into Query Variables full value stored in the Properties it is processed fine. Question: Can I use value from the Properties (saved as a String, I assume) in the Query Variables that is expecting to get JSON object?349Views0likes1CommentMemory problems with 3.40.0
Started having problems with ReadyAPI 3.40.0 after update to this version: Application shut down a few times without saving Cannot save the project: "Java heap space" error Complain while running project asking to increase Xmx in the ReadyAPI.vmoptions file. Current values there are: -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -Xms128m -Xmx1024m2 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes9CommentsRe: Use of global/project property on setting Database Configuration
Hi Rich! Thanks again! For your first question the answer is yes - it works fine if password is hard-coded. For you second question the answer is no: I had problems connecting to postgreSQL using user & password in the JDBC drivers configuration and was advised by Smartbear to not use it there. I might try again to add new postgreSQL driver with "?user=<USER>&password=<PASSWORD>" at the end and try to use parameter there. Regards, Mikhail3 years agoPlace ReadyAPI QuestionsReadyAPI Questions819Views0likes0CommentsRe: Use of global/project property on setting Database Configuration
Hi Richie! Thank you for your response. Here are two screenshots of the PostgreSQL DB config screen: 1. Working with hard-coded password 2. Not working with parameterized password value. I tried both 'as is' value' and percent-encoded: Thanks again!3 years agoPlace ReadyAPI QuestionsReadyAPI Questions838Views0likes2CommentsUse of global/project property on setting Database Configuration
Hi guys, I'd like to stop using hard coded values for setting Password on each Database configuration: I have multiple databases for multiple projects/environments and passwords changing every month. When I tried to use global/project property to store passwords - to have all of them at one place - I do not see that password property parameter I'm trying to set during configuration is being read. Here is example for storing it as Project property: password | context.expand( '${#Project#dataUserPass}' ) Is there a way to use a parameter in this situation? Thank you!882Views0likes4CommentsRandom value in the GraphQL Header
Hi! For each graphQL call I need to submit executionId UUID value as one of the Headers values. Is there a way to use something like "${java.util.UUID.randomUUID()}" directly in the Headers to generate brand new id on the fly? Currently it's not generating any value and sends empty string so I have to use previously generated property value. Thanks!Solved607Views0likes1CommentRe: Using GraphQL without ability to point to a schema file
Hi NBorovyh, Natalie, Thank you for your reply to my question. For #1 - that is unfortunate since other tools I'm using doing that (read schema with provided end point and security token) fine. For #2 - Few comments: I'm dealing with multiple sub-systems that do not provide access to their schemas to me and without that I cannot create API and therefore I'm unable to change end-points for each environment as you suggested. Even if I had access to their schema it would be a huge maintenance nightmare for me to track if any changes are done for any of the schemas - again, this info is not available for me. Best regards, Mikhail4 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes1CommentUsing GraphQL without ability to point to a schema file
Guys, I have a problem to create a project that would work with multiple GraphQL API's in different environments - using ReadyAPI 3.5.1. I can run individual GraphQL test requests fine with hard coded URL, but when I tried to add GraphQL API to the project (to use environment features) I'm blocked b/c I do not have access to the schema files - besides schemas are changing pretty frequently. Two questions: 1. Is there a way to add GraphQL API to the project using End Point and Token to read the schema? Other applications like Altair doing that fine, but for some reason I do not see this option in ReadyAPI. 2. If #1 does not work, can I use for GraphQL's test requests an environment OR project property to specify URL for the GraphQL request for each environment?Solved4 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes3CommentsJDBC call stopped working in 3.0
Oracle JDBC call relying on SSL Authentication from the stored key file stopped working after installing 3.0. Getting back: "ERROR: java.sql.SQLRecoverableException: IO Error: IO Error General SSLEngine problem, Authentication lapse 0 ms"Solved5 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1Comment