forum.e-valid.com

I have to test
1) HTML interface
2) SOAP without HTML interface
I plan with having access to real-world
3) HTML portals
4) SOAP endpoints (WSDL)
sometime next week.

Thanks for posting...

eValid is optimized for #1 and #3, as you may have seen.

If you are driving a SOAP interface direct (without an HTML
testbed for the individual functions) then you probably need to
do that from PERL or Ruby or something like that. The test
driver (test harness) often is very different technically.
You mentioned soapUI I think, and it is a Java app on the
desktop that drives the protocol.

Considering that SOAP services support web interfaces, it
may make sense for you to build a simple test harness for
your particular services at the HTML level. This reduces
the issue to a "previously solved problem", i.e. #1 or #3.

Sorry, we currently don't have another way to drive SOAP
endpoints except from an HTML page...