ReadyAPI 3.56.0 does not fail testcase if iteration in datasource fails
Hi, We have a datasource which takes data from excel to feed in the request. This excel has multiple rows, each row creates a different request and each row gets it's own assertion data. Since release 3.56.0, it seems like whenever an iteration fails from the datasource that is NOT the very last row in the datasource, the test case will still be reported as passed. As a workaround, I'm trying to create a custom testcase property "hasFailed" with a standard value of "false". Whenever an assertion fails, the testcase property is set on "true", but whenever I try to execute the follow script in my test case teardown script: def hasFailed = testRunner.testCase.getPropertyValue("hasFailed") if (hasFailed == "true") { log.info(hasFailed) testRunner.fail("Testcase failed, check transaction log for more details") } it doesn't seem to work. The log.info is displayed but the testRunner.fail doesn't fail the test case itself. Any tips on how to fix this?
Specifying a specific Schema when connecting to Postgres Database Connection
Hi all .. I have no trouble connecting my ReadyAPI application to a Postgres database. However, I need to specify a specific schema to connect to. Say the schema i need to connect to is called bluesky how do i modify my connection string so that the queries hit that specific schema? jdbc:postgresql://0.0.0.1:5432/oompaloompa?user=player1&password=PASS_VALUE
Rest request attachments multipart form data for json file with parameterized json data
So I have been trying to do a scenario where i have two attachments for a rest request, one json file which i need to parameterize couple of fields from previous request. The problem with this is once you have cached the attachment you cannot modify it based on the previous test steps, So i have followed the following youtube linkhttps://www.youtube.com/watch?v=iL-zehJmtWw Used query parameter to use a locally store file of json to request but we are getting the error from response that application/octet-stream content type is not accepted ------=_Part_01_136051460.1696260652738 Content-Disposition: form-data; name="testFile" testFile:/Path/to/file/testFile.json I have used parameter like this testFile:${projectDir}/testFile.json What should I do in this casereadyapi Database connection
in our project, when I add a datasource step and try to add, and choose JDBC as Data Source, and try to add connection I get a pop that says "Connection properties have changed. Do you want to build a query?", I choose Yes to see table like the screenshot below, since I want to select visually database and fields, but it takes very long time like 7 mins to see all databases, is this something expected to take that long, or is there any other solution for that? It is large database, so is there anyway maybe that readyapi does caching?? or any other solutions for large database.
Passing comma separated values for a property in Data driven test case
Hi, I am creating a grid data driven test case using Ready API. For one of the properties, I have to pass multiple comma separated values for a particular property in my REST request. I am not getting how to split the property value in request editor into multiple strings as otherwise the value is being passed to request as single value. Please guide if there is any direct support for processing such data or I need to use groovy script? The grid data looks like: The request snippet is as below:
How to disable "autocorrect/autofill" on SOAP requests
Using ReadyAPI to do a data driven test against a SOAP API. On each iteration, putting XML in the values for a properties test step. This is so that we can have some tests with missing elements, or other structural options. Using a placeholder in the SOAP request to grab those property values (see image). Whenever I save the project, ReadyAPI goes into my request, sees missing elements (because the placeholder puts them there during runtime) and "helps" me by shoving empty element tags in there for schema compliance. Next time I run the test, it fails because of extra tags... I have to remember to go into the request and delete the extra tags. One day I may forget and raise an embarrassing defect. Main Question: Is there a way to disable this "help" that keeps making things more complicated? (please support negative test cases - they're critical for robust testing) Thanks
