Contributions
Re: List DataGen Truncates Last Character
Sure, I've attached a simple Test Case that I created that contains a DataGen Test step with 1 List item - the number 123. Simply click the Evaluate all STEP properties button and check the Last column where you should see the output is 12 instead of 123. Again, this is in SoapUI Pro 4.5 Beta 2. Thanks for looking into this.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions962Views0likes0CommentsList DataGen Truncates Last Character
Steps to Reproduce: Create a List Data Gen item Enter false into the Configuration area. *Do NOT press enter to break to line 2 Run the generator Expected Result Generated property value should be false Actual Result The property value returned is fals. Essentially the last character, no matter the string entered, is always truncated by one character. Side note: If you break to a new empty line it returns the value in its entirety. Win7 SoapUI Pro 4.5 Beta 213 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes3CommentsRe: Environment Endpoint Property Expansion Syntax
Please pardon my noobness but I didn't realize that there was a difference between the two. I guess I should ask a more direct question then. Is there any way to assign the currently active TestRequest endpoint to a TestSuite Custom Property via Groovy or some other means? I've been attempting to take a crash course in Java/Groovy in order to decipher the javadoc to no avail so a brief, simple explanation along with some sample code would help tremendously. Thanks in advance for your help with this.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions655Views0likes0CommentsDataGen Formatting Error
I attempted to generate random email addresses by using the DataGen Number type with the following parameters set: Start: 1 End: 500 Pattern: test#@test.com Randomize instead of step - checked Expected Output: test365@test.com Actual Output: test365.@testcom For some reason the period is removed from .com and shifted to before the @ symbol. I've found a way to work around this by simply generating a name and number and using property expansion to prepend the value before an email extension but thought this was still a bug worth reporting. Please review and advise. Thanks! SoapUI Pro 4.5 Beta 213 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsEnvironment Endpoint Property Expansion Syntax
First, a bit of context. I've created a REST test in which I'd like to swap out endpoints to run the same test against different environments. While doing so I noticed that when I assign an endpoint to 'All Requests and All TestRequests' the endpoint isn't always applied to all Test Requests as it does for a SOAP test. This has several adverse effects, one being that I'm never quite sure whether or not all of my test cases are running against the correct environment, and two, the XPath Assertions and Property Transfers often fail because the namespace is hard coded to whatever environment I created the test with. To circumvent these issues, I've created a custom property in my Test Suite called "Endpoint" in which I manually enter the Endpoint location. Then I use the following property expansion ${#TestSuite#Endpoint} and apply it to all of my Property Transfers and Assertions. Not as seamless as I'd like it to be but it works. However I've recently come to find out that there is an Environment property expansion option and I'd like to use that instead. What I'm trying to do is pull the endpoint from the active environment that I applied from my Test Suite but I don't know the proper syntax. I tried ${#Env#Endpoint} but that didn't work. I've attempted to follow read the documentation as well but have no experience with either Java or Groovy so I found it difficult to follow. Can anyone help?!13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes2Comments- 13 years agoPlace ReadyAPI QuestionsReadyAPI Questions560Views0likes0Comments
Renaming Method Parameters in Method Viewer
I've come across an issue when attempting to rename a parameter in the Method Parameters tab in the Method Viewer. I have a parameter named userID that I'm trying to change to all lowercase - userid. However, when I make the change it reverts back to the original camel case spelling. I have to rename it to something else or clear the field altogether just to rename the parameter. Not a major bug but minor annoyances like this tend to add up.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes2CommentsPassing REST Parameters in the body of the request in JSON
I am trying to test a REST service and have come across what appears to be a limitation with SOAP UI Pro. Our service was initially setup to accept a REST request via query string. However, it has since been refactored to pass the parameters in the body of the request in either JSON or XML format instead. Initially, I was elated to find the Post QueryString feature that allowed the Method Parameters I had created for each call to be injected into the body of the request. Unfortunately, as the feature's title suggests it is injected in QueryString format, which is not supported by our service. Presently, when the Post QueryString option is selected it defaults to Media Type "application/x-www-form-urlencoded" and is uneditable. Does anyone know of a way to have SoapUI inject the method parameters into the body of the request in JSON format? Example: Initial Setup URL: api.company.com/login.json?param1=true¶m2=false Post QueryString Format URL: api.company.com/login.json Body: param1=true¶m2=false Required Format URL: api.company.com/login.json Body: { "param1":"true", "param2":"false" } Not sure if this is a bug as much as it's a feature request but any help would be greatly appreciated! Thanks in advance!13 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.1KViews0likes0Comments