Makarand,
I understand that you some 40-odd
applications and one SOA solution to Test. But before I jump to offer a
solution, I have couple of questions.
1>Is your SOA solution all based on WS
or it includes use of REST, POX etc?
2>How many distinct end points (based
on WS or other mechanism POX)?
2>Do you support multiple bindings (RPC,
Doc lit)?
3>Do you support multiple bindings over
different security mechanisms (RPC over SSL, DOC-Lit over SSL, RPC-WSS, DOC-Lit
–WSS)?
4>Do you support Endpoints with
different API (i.e. XML Schema slightly different for different clients)?
Prashant Sarode
From:
[email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Samir Kumar Mishra
Sent: Saturday, March 11, 2006
7:18 AM
To:
[email protected]
Subject: Re:
[service-orientated-architecture] Testing SOA / Web Services
Makarand,
Given the problem scenario, I would recommend the following.
1. Perform Unit Testing, System Testing and Performance testing for the core
application first.
2. Publish the Test Scenarios to other application testing team and
cross-verify that you have covered all the scenarios for the core application.
3. If the applications using the Core system have more requirements or they are
planning to use the Core app in a way (not covered in ur testing) then add that as a part of the
core testing.
While this will ensure that core system meets all the requirement and will save
time in testing as well.
Coming to number of instances for the application. IMHO you need only one
instance of the core system as all the other apps will ensure that the test
data they create is being deleted by them unless those data also have to be
tested across applications.
Hope this helps
Cheers :)
Samir Kumar Mishra
Tel: +61-403-747-809
Email: [EMAIL PROTECTED]
Home: http://samirmishra.tripod.com/
My Attitude in life is best described by my Blood Group… B +ve
On 3/11/06, catcher_scope
<[EMAIL PROTECTED]> wrote:
Hi,
I need some help on this scenario
1) The core project has built a SOA solution that acts as the System of
Record for around 4 entities. The SOA solution would undergo a User
Acceptance test before integrating applications(around 30 at this point
of time) start using it.
2) Each integrating application would go through its SDLC(Unit testing,
System testing, Perf testing, User Acceptance testing etc). We are also
planning to have an integration test that tests the business process
across ALL applications.
In this scenario, How many distinct instances of the core SOA solution
(Web services plus the database) would be needed to ensure individual
applications can do their unit testing, System testing etc without
conflicts/dependencies ?
Thanks
Makarand
**************************************************************************
This message and any attached documents contain information
which may be confidential, subject to privilege or exempt from
disclosure under applicable law. These materials are solely for
the use of the intended recipient. If you are not the intended
recipient of this transmission, you are hereby notified that any
distribution, disclosure, printing, copying, storage, modification
or the taking of any action in reliance upon this transmission is
strictly prohibited. Delivery of this message to any person other
than the intended recipient shall not compromise or waive
such confidentiality, privilege or exemption from disclosure as
to this communication.
If you have received this communication in error, please notify
the sender immediately and delete this message from your system.
*****************************************************************************
SPONSORED LINKS
YAHOO! GROUPS LINKS
