Contributions
Disable/Enable option for setup andteardown scripts at all level
Please include option to disable/enable setup and teardown scripts at all levels. Currently if the setup and teardown scripts are same, and project is run at the project level, the setup and teardown scripts for testsuite and testcases are also run, which is redundant. Adding these options would increase the modularity of setup and teardown scripts. User wil be able torun project at any level and choose at what level the setup and teardown scripts should run.1.7KViews1like1CommentRun project setup script from testsuite setup & teardown script/ setup & teardown script chaining
Hi, Is there a way I can get the setup/teardown script of project to run from testsuite setup/teardown script and implement same for testcase. I have same setup/teardown script for all levels. If I add setup script for every level testcase, testsuite and project and run it from project, it runs setup script 3 times which is redundant. I want to write setup/teardown scripts for project and chain them for lower levels by referencing/running the project setup script in testsuite/testcase setup script. So irrespective of what level I run , the setup/ teardown script runs only once7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes1CommentRe: jsch session instance
nmrao I understand that. It was some issue where it gave me an error that the post was failed. I refreshed my profile a couple of times but there was nothing, so I kept trying. And after a while there were three questions in my profile. As you can see from the time difference of the questions. I tried finding an option to delete the redundant ones, but its not there.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes1CommentRe: jsch session instance
Hi, I am using jsch session in multiple test cases. I setup server at start of the testcase and close the session at the end using groovy script. Server setup code : import com.jcraft.jsch.Session; def servName = context.expand( '${#Project#servName}' ) ServerConfig servCon = new ServerConfig(servName) def session = servCon.serverConnect(servName) context.testCase.metaClass.session = session log.info("Connected") Session closing code: import com.jcraft.jsch.Session; def session = context.testCase.session session.disconnect() This works fine when testcases are run sequentially. However, throws error when they are run in parallel. ERROR:An error occurred [session is down], see error log for details ERROR:An error occurred [connection is closed by foreign host], see error log for details I am guessing either it is not recognizing the individual sessions or closing all sessions when any of the testcase finishes and rest of them throws the error. I would want to mention that whenever Ready!API is launched and run the testcases do run in parallel without any issues. But in the second run they throw this error. Is there a issue with how I am passing the instance?7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes3CommentsRe: jsch session instance
Hi, I am using jsch session in multiple test cases. I setup the server at start of the testcase and close the session at the end using groovy script. Server setup code : import com.jcraft.jsch.Session; def servName = context.expand( '${#Project#servName}' ) ServerConfig servCon = new ServerConfig(servName) def session = servCon.serverConnect(servName) context.testCase.metaClass.session = session log.info("Connected") Session closing code: import com.jcraft.jsch.Session; def session = context.testCase.session session.disconnect() This works fine when testcases are run sequentially. However, throws error when they are run in parallel. ERROR:An error occurred [session is down], see error log for details ERROR:An error occurred [connection is closed by foreign host], see error log for details I am guessing either it is not recognizing the individual sessions or closing all sessions when any of the testcase finishes. Rest of them throws the error. I would want to mention that whenever Ready!API is launched and run the testcases do run in parallel without any issues. But in the second run they throw this error. Is there a issue with how I am passing the instance?7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes0Commentsjsch session instance
Hi, I am using jsch session in multiple test cases. I setup the server at start of the testcase and close the session at the end using groovy script. Server setup code : import com.jcraft.jsch.Session; def servName = context.expand( '${#Project#servName}' ) ServerConfig servCon = new ServerConfig(servName) def session = servCon.serverConnect(servName) context.testCase.metaClass.session = session log.info("Connected") Session closing code: import com.jcraft.jsch.Session; def session = context.testCase.session session.disconnect() This works fine when testcases are run sequentially. However, throws error when they are run in parallel. ERROR:An error occurred [session is down], see error log for details ERROR:An error occurred [connection is closed by foreign host], see error log for details I am guessing either it is not recognizing the individual sessions or closing all sessions when any of the testcase finishes. Rest of them throws the error. I would want to mention that whenever Ready!API is launched and run the testcases do run in parallel without any issues. But in the second run they throw this error. Is there a issue with how I am passing the instance?7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes6CommentsRe: jsch session instance
Hi, I am using jsch session in my test cases. I setup the server in first step(groovy) of every test case and close it in last step(groovy). I am currently using following code: Setup server code: import com.jcraft.jsch.Session; def servName = context.expand( '${#Project#servName}' ) ServerConfig servCon = new ServerConfig(servName) def session = servCon.serverConnect(servName) context.testCase.metaClass.session = session //Note: ServerConfig is a library. Session Disconnect code: import com.jcraft.jsch.Session; def session = context.testCase.session session.disconnect(); This works for multiple test cases running sequentially. But when I runt testcases in parallel I get following error: ERROR:An error occurred [session is down], see error log for details I am thinking this is due to one of the test cases finishing early and running session disconnect code, which disconnects all session. Please help how can I run test cases in parallel, with individual sessions running and closing.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes0CommentsRe: Clone Datasource using groovy script
Hi, I found a work around for this. I used groovy script to set data in property step. Added a property "rows" in property step which would determine the number of rows in datasource. Used this propery in number of rows field of datasource. This let me manipulate the datasource upto some extent.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes0CommentsRe: Clone Datasource using groovy script
the properties are same in all three so that is not the problem. The values and number of rows changes. What you are suggesting is also feasible, just need datasource to reflect src 1 or src 2.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes0Comments