|Web services testing. [message #26129]
||Wed, 10 August 2005 13:33
Originally posted by: ada_nospam_m._No_softfab_Spam.com|
I appologise in advance for posting to 2 newsgroups however I am unsure
which group would be dealing with this.
I work for the UK NHS & we're in the midst of a fairly large health care
project. A large part of this involves pushing XML messages about the
place via SOAP etc.
We end up it an interaction diagram which in essence looks like
System A System B
Message1 > Received
Received < Message2
Message3 > Received
Received < Message4
etc. showing the which XML messages are sent in which order.
We'd like to be able to automate the testing of this to a degree & are
in the midst of looking at creating some Eclipse plugins to cover the
entire lifecycle from inception through modeling to testing.
What I was wondering is that given the above can be fairly easily mapped
into an XML file we should be able to autocreate a testsuite from it (at
the very least at the schema checking level).
i.e. Supplier A sends us Message1 which we receive & test with a
schemachecker. We then want to reply with a test message conformant to
the schema of Message2 etc.
There might be a fairly lengthy conversation involving a fair few
different messages flying backwards & forwards. We want to be able to
produce a test report (at the very least for the schema compliance of
the messages received in the conversation) & we want to ensure that the
messages are received & sent in the right order etc.
I am wondering if there is anything within the TPTP or webtools which
can create the 2 relevant webservice stubs.
We might then at some point want to fit content checking & bouncing
(i.e. if this value should be returned, pull it out & put it into the
reply) etc. but that's someway down the road.
We'd want stubs for both sides of the conversation so we could check our
own replies before letting the test out into the wild for suppliers to use.
It should be possible using something like servlet filters as we are
only caring about the XML as an XML document (message/payload) & would
not need to test the outer layers of the onion (i.e. the soap layer, the
security layer etc).
Powered by FUDForum
. Page generated in 0.03083 seconds