Contributions
Re: Close JDBC connections following JDBC datasource step
From my initial investigations - no. The session only seems to be killed if I go into the DB and kill the session via the SYSTEM user. I'll do some more checking of this though to make sure that's exactly what's happening6 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes0CommentsRe: Close JDBC connections following JDBC datasource step
Hi Richie, and thanks for the reply. Apologies, I should have mentioned that. It's an Oracle database. From what I can tell, in the JDBC step I can only enter one query/command. So I'd have to create a new JDBC step to run the KILL SESSION command, which would kill that session and leave the first one open.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes0CommentsClose JDBC connections following JDBC datasource step
Hi all, We have built a set of test cases that follow the steps below: 1. JDBC DataSource Step - this step connects to our database and pulls back a set of data that we will use in our request message 2. REST Request Step - using the first value returned from the above JDBC DataSource step, we will send a request to the REST service and assert the values against our expected result 3.DataSource Loop - loops back to step 1 to pick up the next input value However, we have found that the connection to the databasethat is established in step 1 is never closed. Our databases have session limits, which means that we quickly bring down our databases and require a database restart in order to continue. Is there a way to ensure that the database connections are closed, either after step 1 has run or at the end of the test? Thanks in advance for your help. Matt6 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes5CommentsRe: JDBC Status assertion fails only when running at the test case/project level
Thanks for the suggestions both. I have split the test steps into individual test cases now, so rather than one test case having multiple JDBC test steps, each test case only has one JDBC connection. This seems to have fixed the issue, although I still don't really understand the root cause. Thanks again for the help. Matt6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews1like1CommentJDBC Status assertion fails only when running at the test case/project level
Hi all, I've just created a new test case that creates a new Oracle user, gives it a specific role and then runs a set of SELECT queries to ensure if it has access to the views that it needs. To do this, I've added a set of JDBC Request Test Steps. Each one just has a simple select statement (i.e. select * from *view name*). Each step also has a JDBC Status assertion which acts as my pass/fail (i.e. if the user doesn't have access to a particular view, that step will fail). When I run each test step individually by clicking the play icon on the test step level, each step passes. However, when I run the test case as a whole (by clicking the play icon on the test case or project level), a number of my test steps fail with the error: "table or view does not exist". However, when I then click on one of the failed test steps and re-run the test step at the step level it then passes. Any idea why this could be happening and how I can resolve the issue? Thanks in advance for your help, MattSolved6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes5CommentsRe: How to test a JSON response with multiple objects with the same name
Hi Richie, We could have different number of test1 instances returned depending on the scenario. For example, we could request to see all of our customers in Lincolnshire which could return 100 instances of test1 - whereas requesting to see all of our customer in Scotland may return 300 instances. Hope that makes a bit more sense. I've had a look through the other posts that seemed to be linked to this request, but none seemed to answer this specific query. I'll have another scan through them now to check the most recent responses. Thanks, Matt6 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes0CommentsHow to test a JSON response with multiple objects with the same name
Hi, I'm looking for some ideas on how we can test one of our new API's.The API in question will return a JSON response similar to the one outlined below: { "testJSON" : [ { "test1" : "111", "test2" : "ABC" }, { "test1" : "222", "test2" : "DEF" } ] } As the JSON response can have multiple objects with the same name (e.g. we will have multiple objects called test1), we've been having difficulties finding a way to create assertions to allow us to check that the each object contains the correct value without manually creating properties for each object. Ideally, we want to be able to use an Excel spreadsheet which will show each JSON section on a separate row (e.g. the columns will be titled test1 and test2 and each row will display the expected content for each section of the JSON). We'd then want an assertion test step to compare the JSON response to this spreadsheet. We've tried a few methods of doing this in SoapUI (we've tried data sources, assertion test steps, data sinks etc) but they all start to fail as soon as we have more than one object with the same name. My guess is we'll need to write a groovy script to do this, but I just wondered if anyone had any experience with JSON's in this format and how they managed to get around the above issues? Please let me know if you want me to add any more info into the question. Thanks in advance for your help. Matt6 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes2Comments