Process of Manual Testing of Service

The document describes the process of manual testing of a service including preparing test data, parameterizing XML requests and responses, executing tests, validating responses by comparing to expected output, and handling different error situations. It also provides descriptions of key concepts like publish-subscribe patterns, queues vs topics, WSDL files, and the need to parameterize tests and create test data in Excel or other formats.

Uploaded by

Sai Krishna

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

86 views

Process of Manual Testing of Service

Uploaded by

Sai Krishna

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 5

ITKO lisa

Process of Manual Testing of Service Analysis of the service 1. GO through the IDD document 2. Prepare high level design document 3. Make note of the QUEUE and PUB been used in the service 4. Before testing, verify the QUEUE and PUB is available. (Hermes JMS of SOAPUI is been used to verify) 5. Preparation of Unit data 6. Preparation of Functional test data 7. Parametrizing input Request XML and Expected Response XML 8. Parse (Replacing with current values which ares stored in Excel sheets the input and response XMls) 9. Compare Expected Response with Actual response 10. Validations points may be of logs ,Database, Response Xmls

11 validation point is the logs of another web service (PUB-SUB model) Assertions: Xpath XML-XML Comparision( Comparing Expected with Actual) script assertions

Publish-Subscribe Model Described as events or pattern of events produced by publishers that subscribers interested in and notified when they are available.
Functionality of Publish Service Receives event from the Applications (Publishers) to notify Subscribers. Sends event of a particular queue to Applications (Subscribers) who has been subscribed for that queue. s Functionality of Subscribe Service Exposes method which an: application (Subscriber) can remotely invoke through communication channel to subscribe queue wise for getting events.

Functionality of Subscriber: Subscriber application registers itself for one or more queue event. Receives event when event is sent from publisher.

Functionality of Publisher: Sends event to publisher Service for publishing

Let's suppose we have an website that allows new users to register themselves (the event publisher). There are certain actions that need to happen when a new user has successfully completed the registration form (the event subscribers):

The database needs to be updated with the user's information. The website owner needs to be notified that a user has registered and will need to approve the user before they can actually use the site. The new user will need to be sent a "welcome to our site" type message. The site will need to set a cookie in the user's browser so they will be "recognized" the next time they visit the site.

Semantic events are programmatic and involve the developer to create their own events, subsequently creating listeners to take custom actions based on those events.

Events are a critical component in Object Oriented programming. Whether they originate from user interaction or code logic, events are at the heart of what makes your application dynamic.

There are generally two types of events in Java and .NET; low-level events and semantic events.

Low-level events typically involve OS (GUI) type events such as Mouseclicks (onMouseClick, onMouseDown, etc) or keyboard actions (onKeyPress, onKeyDown, etc) whereas Semantic events are programmatic and involve the developer to create their own events, subsequently creating listeners to take custom actions based on those events. This article is geared toward utilizing semantic events.

INPUT AND OUTPUT XML For every Application there is different workflow between the methods or services. These different methods or services communicate/transfer information amongst in the form of XMLs. The Input XML hits the web service and an Output XML is generated as response. This O/P message has to be validated as a well formed XML Schema (i.e. with proper structure and data of the messages).

Parametrizing the request & adding data Set Parameterizing is very important, especially when it comes to Data Driven testing as test should contain various data inputs. In order to achieve this, each web service request should be parameterized and the dataset added to ensure same request is executed with multiple sets of test data for better test coverage. This will be your input excel file. Parameterizing the request Enclose all the tags which needs to be parameterized in {{ }} braces. Create an Excel having all the tag names which need to be parameterized as the column; with a set of values and save this excel on to your machine. Test execution status based on validation. Add a Java script step Adds in model Java Script Step to set test execution status based on validation. This script case is re usable for any test case, variables needs to be changed. E.g. If Extracted response using xpath matches expected data in the above sheet, set test case status to pass or else fail. Test execution status based on validation. Add a Java script step Adds in model Java Script Step to set test execution status based on validation. This script case is re usable for any test case, variables needs to be changed. E.g. If Extracted response using xpath matches expected data in the above sheet, set test case status to pass or else fail.

Different situations where we may face issues: Database is down Logs are not updated(JMS Triggers are disabled or down)

NOTE:Error logs are referred during testing process and validation process when required and applicable. Generally Sub service will either connect to database or application
MQ server is IBm web sphere Queue contains both queue and topic Use JMS to connect to any queue server

Queues: It is used for exchanging messages between programs which are independent of each other, at different locations and without having any logical connection between them.

Topic: It is similar to a queue; however in a topic every subscriber listening on that topic will receive a copy of the message.

WSDL It contains all the methods which are present in the Web Service. Apart from that it mainly describes about binding i.e. how the end point communicates. A WSDL document defines the following objects in a web service execution: 4.1 4.2 4.3 4.4 Types It describes the data and XML Schema is used to verify that. Message It depicts the information needed for execution of operation. Operation the operation supported by the Web service or methods. Port Type defines a web service.

4.5 Binding It defines the interface, binding style and transport used for communication (HTTP etc.) 4.6 4.7 Port Defines connection point to a web service. Service- Set of endpoints.

TEST DATA While using an Input XML, we need to parameterize its tag values so as to cover different scenarios for the various tags. Now after parameterize, we have to create a test data with different set of test values for the tags. This Test data can be of different forms, but usually it is created in Excel format as the values can be assigned/modified easily as per the change in Test Scenarios. Else the values can be picked from database, or we can create a data set in the Lisa itself.