Web Services Test Policy

stalksurveyorΑσφάλεια

3 Νοε 2013 (πριν από 3 χρόνια και 10 μήνες)

77 εμφανίσεις

Policy

Name

Web Services
Test

Policy

Version

0.2

Status

Draft

Approval Date

Next Review Date

Owner

EGAB

Purpose

Specifically define
s

what constitutes an EGAB acceptable
web services
test
.

Scope

Service Integration and Test.

For all web services that are to be published at an enterprise level must be
tested using sound and proven test methodologies
. This policy specifies a phased approach that is very
generic so that it can be easily applied to any web services testing.

Respo
nsibilities

The web service provider or the entity that makes a web service available in the Registry/Repository is
responsible to

comply with this policy
.

Compliance

Plan

Web services will not be approved for enterprise access without
a successful end
-
to
-
end test and
documented in the Integration Test Report Policy, Non
-
Function Test Report Policy and the Acceptance
Test Report Policy.

Statement



EGAB does not provide or endorse a specific test tool, utility or
detailed
methodology. The web
service provide
r can utilize their resources of choice given that such choices can successfully
complete a full end
-
to
-
end test of the service.



Due to the nature of web services, testing should follow a phased testing approach:

o

Governance Testing



Ensures that SOA
policies are met and adhered to.



Ensures that all individual service components follow policies and the service, as
a whole, meets those policies.

o

Unit Testing



This is essentially a unit test that ensures each
code
component functions as
required
.

o

Service
-
level
functional
testing



This is a functional test of the service that ensur
es operation perform according
to requirement.



Includes negative testing to ensure that exception handling is robust.

o

Service performance testing



Load support, response time testi
ng.

o

Integration
-
level testing (Integration Test)



Ensures that each web service successfully meets expectations for all points of
integration/interface.

Performed by consumer.

o

Process/Orchestration
-
level testing (Process Test)



Ensures services are operatin
g collectively as specified.



This phase of testing would cover business logic, sequencing, exception handling
and process decomposition (including service and process reuse).

o

System
-
level testing (Acceptance Test)



System Level testing will form the major
ity, if not all of the User Acceptance
Test phase.



This test phase will test that the SOA technical solution has delivered the
defined business requirements and has met the defined business acceptance
criteria.



Performed consumers

o

Security Testing



Ensures

that all security has been properly applied.



Ensures systems and data are properly secured to prevent unauthorized access.


Change log

Version
Number

Date

Revision Author

Description

0.2

03/23/09

EGAB

Refined statements