hazem_borham
Occasional Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: SOAPUI 4.6 Cursor Location
Pheww, I'm not the only one with this annoying issue. Seems like the work-arounds, lower resolution, is the best option, makes soapui look blurry though. Found some interesting reads about Retina and Swing applications, seems like the jre's between 6 and 7 might be where the differences in experience are seen. For instance the apple distributed jre 6 had support for retina, but oracle's 7 did not. http://stackoverflow.com/questions/1518 ... -awt-swing http://apple.stackexchange.com/question ... na-support1.3KViews0likes0Comments[Reg] Auth Compatibility Issues with soapui 5.0.0 and 4.x
Not sure if this is a bug or usage issue with the new features in soapui 5.0.0, but let me try and explain. In short, projects set-up in 5.0.0 are not always compatible with 4.5.1 and/4.6.4 due to the change in default for Authentication Type . The following are some errors seen by the TestCaseRunner in automation: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: string value 'NTLM' is not a valid enumeration value for type of authType element org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: string value 'No Authorization' is not a valid enumeration value for type of authType element. Example Usage Pattern It looks like there are new features in 5.0.0 for setting up Auth, the change in behavior has an impact for users defining their tests in 5.0.0 and automation running on a 4.x version. Specifically in the case of what would be "Basic" in 5.0.0, a user in 4.x could set up Username, Password, Authentication Type, WWS Password-Type via the TestRequest Properties window. From the Auth tab of the request, Username, Password, and Authentication Type are configurable and NOT WWS Password-Type. In addition the default value for Authentications Type in 4.x was "Global HTTP Settings". A common pattern for test configuration was to use only the TestRequest Properties window to configure the 4 options noted. In 5.0.0, the Authentication Type changed the default from "Global HTTP Settings" to "No Authorization", and is no longer configurable/editable on TestRequest Properties. The only way to configure the same case on 5.0.0 is always edit in the Auth tab and then change WWS Password-Type in the TestRequest Properties. If a 5.0.0 user creates a case with Authentication Type equals "No Authorization", then the 4.5.1 runner (and UI) will choke, the runner will throw this error when trying to run the request: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: string value 'No Authorization' is not a valid enumeration value for type of authType element. Since "No Authorization" is a new option for 5.0.0 and "Global HTTP Settings" was the default, I think making "Global HTTP Settings" should be the default in 5.0.0. In addition, please make Authentication Type editable in TestRequest Properties in 5.0.05.5KViews0likes4CommentsRe: [Res] Not being able to import WSDL's in SoapUI Pro 4.6.4
I believe this is a bug in soapui 4.6.4. The code change although relatively small caused the change in behavior. The load(url) returned a ByteArrayInputStream used to create the XmlObject. Now the code gets the ByteArrayInputStream converts it to a String, does some magical stuff to fix the issue relating to the code change, converts the string back to bytes[], and then the bytes[] is used to create a "new" ByteArrayInputStream that is used to create the XmlObject. The problem is converting this down to a String and then back to bytes[]. In the process the original wsdl's encoding and charset is lost since String getBytes() will convert based on the jvms file.encoding setting. The fix would be to preserve the encoding of the original wsdl and use this in getBytes(Charset charset) instead of getBytes().7.2KViews0likes0CommentsRe: Project Coverage report
1) This seems like it would be a useful feature when running multiple projects, and rolling up results to one report. 2) This csv is availabe thru the UI, Project > TestSuites tab> Project Coverage tab. Click the Create Report Button Select Format = Data Export. Select the Project Coverage checkbox. Select Format = CSV. Select checkbox for Include Header Row. ....This is the csv file I mentioned earlier. Is this available to create via the testrunner.bat?800Views0likes0CommentsProject Coverage report
I have a couple questions that relating to the Project Coverage report 1. Is there a way to produce one Coverage report for many Projects (similarly to the junit report)? I currently launch all my soapui projects from an ant script, and i added in the -g option, but the result is only the last project run displays in the coverage report. 2. Is there a way to generate the Data Export version of the Project Coverage report in csv format from the testrunner.bat? Thanks in advance -Haz1.6KViews0likes4CommentsRe: TestSuite does not execute a cloned testcase
The cloned testcase is within the testsuite that I am executing, and I am running the entire project. My goal is to clone the master testcase and have both (the master and clone) executed and reported on in junit report. I'd like for this all to happen at run time. Any ideas on how to accomplish this?1.4KViews0likes0Comments