minhng
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: JDBC results are stored in the ReadyAPI project
I have figured out why the test case xml file is growing big. It is caused by the smart assertion in the JDBC-test step. The records in the response are stored in the xml-file. I deleted the assertion and add a subsequent Groovy test step to verify the result. The file size is reduced remarkably.71Views0likes0CommentsRe: JDBC results are stored in the ReadyAPI project
Yes. In my composite project there are one xml file for each test case. The particular test case has a JDBC-request test step to search for a customer with specific attributes to use in the following test steps. The JDBC-response can contain many records and the test case select only an arbitrary one for executing tests on. When I open the xml file in Notepad++ and see that the records from the JDBC response are stored in the xml file. They are not relevant info since I do not need them in the subsequent test run which might need another set of test data from db. I have tried to set the attribute "Discard Response" in the JDBC-Request-TestStep-Properties in ReadyAPI without luck. https://support.smartbear.com/readyapi/docs/functional/steps/jdbc-request.html Or it did work but the data already recorded in the xml file remain... Anyones is experiencing the same?28Views0likes0CommentsJDBC results are stored in the ReadyAPI project
Hi, I see that the search results retured from a JDBC-test step are stored in the test case file in my composite project. It makes the file size turns out to be huge and is impossible to push into GitHub - where the file size limit is 50MB. My question is how to prevent test runs from storing JDBC response in the file and how to remove those in existing files. Thanks in advance.Solved69Views0likes3CommentsRe: How to remove (not clear) test case properties from SaveScript
Hi. I do not have any contribution to resolve this question but I have a similar concern relating to the same. I see that the search results from a JDBC-test step are stored in the project. It makes the file size turns out to be huge and impossible to push into GitHub - where the file size limit is 50MB. My question is how to prevent test runs from storing JDBC response in the file and how to remove those in existing files. Thanks in advance.17Views0likes0CommentsRe: ReadyAPI hangs when running different test cases against different environments in sequence
Hi Rich Thanks for the reply. The problem is gone after I have changed to another more powerful (CPU/RAM) computer. It seems like ReadyAPI turns out to be more resource demanding when running with multiple configured environments. Yes. we have large test cases. But we have not experienced such issue when excuting towards single environment. I close the case. Cheers. -Minh710Views1like0CommentsReadyAPI hangs when running different test cases against different environments in sequence
Hi, I have set up multiple environment configurations in ReadyAPI (Dev, Test and Stage) - each of them include actual endpoints and project properties. It works well when I execute a test case switching between those envrionments in sequence. As soon as I subsequently try to execute another testcase then ReadyAPI hangs and it has to be aborted with Windows Task Manager 😞 Anyone has experienced the same? Appreciate to receive some advices.SolvedRe: Datasource and Datasink Test Step
Hi, Have upgraded to 1.4.1. The issue with storing Properties in Datasink Test Step still persists after the tab is closed. However, the issues with Configuration in DataSource and DataSink Test Steps (Excel file, worksheet, etc...) have gone :-)4.6KViews0likes1Comment