Forum Discussion
Michael_Eddingt
17 years agoOccasional Contributor
I saw that example which is nice, except I want to dynamically inspect the request to determine what fields are there and assign a datasource property to them. I'd like the code to work against different operations.
I had thought about looking at the request xml and searching for the "?" place holder that is put in some fields, but it's not a complete solution.
I'd also like to avoid re-writing the code in SampleXmlUtil.java that looks to produce the example XML. Since you are exposing a forms view I was hoping there were already some helper classes someplace that I could use to "easily" inspect the parameters.
To give a little background on what I'm doing, I would like to run a Groovy script that walks a WsdlProject and creates one or more test suites that performs some standard generic testing of each interface/operation. This currently includes some basic fuzz testing (throwing random values at each field).
I already have working code to create the test suite, test cases, etc. But currently there is a manual step to load each soap request test step and set the property for each field and change the field count in the DataSource code. I'm hoping to remove that manual step.
mike
I had thought about looking at the request xml and searching for the "?" place holder that is put in some fields, but it's not a complete solution.
I'd also like to avoid re-writing the code in SampleXmlUtil.java that looks to produce the example XML. Since you are exposing a forms view I was hoping there were already some helper classes someplace that I could use to "easily" inspect the parameters.
To give a little background on what I'm doing, I would like to run a Groovy script that walks a WsdlProject and creates one or more test suites that performs some standard generic testing of each interface/operation. This currently includes some basic fuzz testing (throwing random values at each field).
I already have working code to create the test suite, test cases, etc. But currently there is a manual step to load each soap request test step and set the property for each field and change the field count in the DataSource code. I'm hoping to remove that manual step.
mike
Related Content
- 12 years agoMartinSpamer
- 2 years agoarmygrad
- 3 years agoKarelHusa
- 4 years agobklabel1
- 13 years agoAnumakonda_mahe
Recent Discussions
- 3 days agoKLWallace