Contributions
Re: OAUTH With REST request
Hi Prakash I am using version 4.5.2 . However i did upgrade but it corrupted by existing test cases so i reverted back to the old testcases The issue is not consistently recreated. It is when i add properties to the testsuite to reuse the accessToken/clientCode and then i can't use that testcase even if i delete the newly added properties if i create another testcase with the steps copied from the old test and it is OK . Thanks and Regards Smitha11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0CommentsRe: Swagger Support
Hi Thanks for the response. Can you please let me know how i can update the resources using the using the swagger api plugin ? i was able to create the initial Resources and testsuite. Now when there are updates to the swagger , if i say "add swagger" it creates me a new rest service . What am i doing wrong ?12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsPassing parameters between test steps.
Hi! What is the best way to pass parameters between test steps? I currently use Property Transfer feature, but I can't find a way to make it more dynamic. Currently namespace contains my server name which changes from environment to environment and will be causing my tests to fail: I have to pass ruleId returned as a response of one test step to another test step: Using property transfer: declare namespace ns1='http://hostA/service/rules/save'; //ns1:Response[1]/ns1:ruleId[1] But I want hostA to be passed as another parameter, I need something like: declare namespace ns1='http://' + ${#Project#SERVER} + '/service/rules/save'; //ns1:Response[1]/ns1:ruleId[1] Is there any way to build the namespace dynamically? Thanks!12 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes1CommentRe: External values should transfer before Project LoadScript
Oooops, sorry. I discovered that what I'm trying to do is available through "Setup Script" for Test Suites (which is under the second TAB in the "Project" window. Not the most evident "place" to find, but very logical once you are aware of it's existence /Tommy12 years agoPlace ReadyAPI QuestionsReadyAPI Questions765Views0likes0CommentsExternal values should transfer before Project LoadScript
Currently, any property values set from outside when running tests from Maven (or any other tool i guess), are not set (transferred to SoapUI) before the Project LoadScript is executed. They are transferred AFTER, when the TestCaseRunner is initiated (se LOG output below) To me, it would seem natural that any info coming from the "outside", would be transferred to the "inside" before anything else happens, since you cannot possibly know when the info is going to used (and what for). Right now the "Project LoadScript" is performed first and then, when the testrunner kicks in, the properties from the POM-file are transferred to the Project properties. Example: Maven POM-file: <projectProperties> <value>ENVIRONMENT=${integration.test.environment}</value> </projectProperties> Command line: mvn -Dintegration.test.environment=si1 test Project LoadScript: def env = context.expand( '${#Project#ENVIRONMENT}' ); (is already saved as "qa1" in the project, and is supposed to be overridden by the external parameter) LOG output: 2012-09-25 15:29:35,048 INFO [log] ###### PROJECT LOAD: Casino2 ###### 2012-09-25 15:29:35,747 INFO [log] Server1: https://www.somehost1.com 2012-09-25 15:29:35,747 INFO [log] Server2: https://www.somehost2.com 2012-09-25 15:29:35,748 INFO [log] ############################## 2012-09-25 15:29:35,755 INFO [SoapUIProTestCaseRunner] Setting project property [ENVIRONMENT] to [si1] The three first lines in the LOG shows the output from the "Project LoadScript", which is performed BEFORE the property transfer from Maven (or any other tool). The value for "Server1" & "Server2" above is set through a lookup which uses the Project property "ENVIRONMENT" (which should have been overridden, but has not and therefore contains the value which was saved with the project). The LOG also shows that the transfer of external values is performed by the "TestCaseRunner", instead of the "Project startup". Best regards, Tommy Pettersson, North Development (Unibet), PI-Test12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes1Comment- 12 years agoPlace ReadyAPI QuestionsReadyAPI Questions607Views0likes0Comments
[Res] Content Assertion not working through JunitRunner?
Hello, Are there any known issue around content assertion not working when we run soapui project files through junit? Here is my code SoapUIMockServiceRunner soapUIMockServiceRunner = new SoapUIMockServiceRunner(); soapUIMockServiceRunner.setBlock(false); soapUIMockServiceRunner.setProjectFile(getClass().getClassLoader().getResource("project.xml").getPath()); soapUIMockServiceRunner.run(); SoapUITestCaseRunner runner = new SoapUITestCaseRunner(); runner.setProjectFile(getClass().getClassLoader().getResource("project.xml").getPath()); String testFilesDirectoryProperty = System.getProperty("testfilesdirectory"); String[] properties = new String[4]; properties[0] = "ENVIRONMENT=S1"; properties[1] = "SERVER=server.com"; properties[2] = "COMPONENT_PORTBASE=22480"; properties[3] = "testfilesdir=" + testFilesDirectoryProperty; runner.setProjectProperties(properties); runner.run(); But i can't see content assertions being asserted when the tests are triggered? Thanks12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes2CommentsRe: [Res] Mockserver support for REST based projects
I cant use standalone stuff for our integration tests as it doesnt fit out process.We want to deploy this war as part of integration testing the main app and get rid of it when its done. Anyways i have allready overridden this mockaswarservlet and implemented that method for now.So all good now. Please make sure that it gets looked into. Thanks12 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes0Comments