Contributions
Re: Problem with UTF-8 encoding in requests
This does work. However I was expecting that because the representation was defined in the WADL as 'application/json; charset=UTF-8' that it would use this by default. Setting the encoding there results in the following request: <request was removed> The charset gets listed twice. which is messy. Thanks for you help this was blocking a bunch of testing.5 years agoPlace ReadyAPI QuestionsReadyAPI Questions18KViews0likes0CommentsProblem with UTF-8 encoding in requests
This is the problem our team is having. "I have a request that is supposed to be UTF-8 encoded when it is sent. We are testing with the following ‘¥£€¢₡‘ it is expected that this would be ‘\uC2A5\uC2A3\uE282\uACC2\uA2E2\u82A1’ but we get ‘[0xa5][0xa3][0x80][0xa2]?[0xa0]’ after some investigation this looks like either Window ANSI 1252 or ISO Latin-1 (iso-8859-1) but not utf-8. I’m not sure how to fix this as there does not appear to be any way to change the encoding that is being used. In the NVP instance i’m pre-encoding the string to be application/x-www-form-urlencoded; charset=UTF-8 using groovy but i’m not able to do this for the application/json; charset=UTF-8 at the moment." The log of the issue is the following: <log was removed> We are seeing this behaviour when the tests ate running from a Windows XP machine. Can you please advise if there is a solution or if this is a bug. Thanks, Gordon.5 years agoPlace ReadyAPI QuestionsReadyAPI Questions25KViews0likes3CommentsSupport for XLSX format Excel files for 256+ data columns
Hello, We are writing complex tests that are requiring more than 256 data columns to support them. Our current data sources are Excel file but SoapUI only supports the older XLS format which has a limit of 256 columns. While we can move to other data source formats like CSV or database, Excel style data sources are much more user friendly. Do you have plans to support XLSX files? We don't want to expend considerable effort reconstructing tests only to find that extended Excel support is just about to be released. Thanks, Gordon.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1CommentUsing the WADL to drive the testing of the responses
Hello, This is a request that came from one of our test developers. I build the request based on 2 things the data and the request definition from the WADL. I do this by relying to the naming convention that the name of the property in the datasource exactly matches the name of the property in the restRequest as defined by the WADL. The result of this is that building the body checks the request definition and then based on the list of allowed properties populates the message body (if data has been provided for that field)To illustrate (code snippet): targetStepHolder.properties.each(){element -> //for every property of the RestRequest Step if (element.value.toString() ==~ /.*RestTestStepProperty.*/){ //test to see of the property is from the WADL or from soapUI if (element.key == 'session') { if (dataStepHolder.properties[element.key].value == "") { jsonMap.addElement(element.key, formSessionID, "string") }else { jsonMap.addElement(element.key, dataStepHolder.properties[element.key].value, "string") } }else { if (dataStepHolder.properties[element.key] == null){ // there is no property here logHolder.error("There is no data column for " + element.key + " in the data store") }else{ if(dataStepHolder.properties[element.key].value != ""){ if ( element.value.getType() ==~ /.*string/){ jsonMap.addElement(element.key, dataStepHolder.properties[element.key].value, "string") }else { jsonMap.addElement(element.key, dataStepHolder.properties[element.key].value,"non-string") } }//end if data column has no data }//end else data step has not column branch }//end if property is a rest element }//end loop for each property What I’d like to be able to do: I’m looking to use the WADL to drive the testing of the responses in the same way I’m using it to drive the message body building scripts. What I need to do this is the collection of properties that the WADL has defined as the ‘Response’ I’ll then use this to interact with the datasource (for all but a couple of exceptions) However I can’t find anything that indicates how to get at the transaction’s defined response fields from the testStep in the same way that I am with the inputs. I’m wondering if this is possible and if so how. Thanks for any help you can provide. Regards, Gordon.14 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.8KViews0likes2CommentsRe: Multiple project files with maven
We'd also find this to be useful. While we can get some of the behavior through use of profiles in the top-level project POM we are having to replicate "out of the box" Maven behavior that should just work. Thanks, Gordon.14 years agoPlace ReadyAPI QuestionsReadyAPI Questions989Views0likes0CommentsRe: No transfer of soapUI's datasource / -loops steps?
This is also true for us. We have existing test automation in SoapUI that uses data driven templates for functional testing. We had hoped to simply import these test cases into LoadUI and run them with different data. however this has not worked. We have automated with the approach of one test cases representing a business function from beginning to end with all related 'transactions' of the system included, the data is one line = one transaction with memory stores for carried data. This requires that each test case has supporting steps that control branching, data manipulation and capture as well as all possible transactions for that business activity. Our most complex test case has 27 steps with 10 of those representing actual transactions (the ones that we would want to report on). Given this approach it would be beneficial if we could also change the dataset used when LoadUI runs the test as opposed to SoapUI. Would it be possible to have an indication of when this would be available in a LoadUI release? Thanks14 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0Comments