Explore topic-wise InterviewSolutions in .

In SoapUI, we can USE GROOVY Script in the following two places.
•Groovy Script Teststep under the TEST case
•Script ASSERTION Test Step

In SoapUI, we can use Groovy Script in the following two places.
•Groovy Script Teststep under the test case
•Script Assertion Test Step

Groovy is a SCRIPTING LANGUAGE which internally includes all the java libraries – it helps US to CUSTOMIZE and add custom validations to SoapUI tests

Groovy is a scripting language which internally includes all the java libraries – it helps us to customize and add custom validations to SoapUI tests

In SoapUI, XPath assertion is USED for asserting the web service response value by SPECIFYING the absolute path. If the absolute path is MATCHED with the response value, then the TEST CASE or test suite will be considered as PASS otherwise it will be notified as FAILED. We can see the results of assertion at bottom of the screen where the Assertion tab will have resultant information.

In SoapUI, XPath assertion is used for asserting the web service response value by specifying the absolute path. If the absolute path is matched with the response value, then the test case or test suite will be considered as PASS otherwise it will be notified as FAILED. We can see the results of assertion at bottom of the screen where the Assertion tab will have resultant information.

In a SOAPUI PROJECT, the following order should be maintained.
•TestSuite – This is combination of functional tests and logical blocks
•Testcase – Its a group that contains several TEST steps for the SPECIFIC aspects of the service.
•Teststep – it contains the SET of functional tests

In a SoapUI project, the following order should be maintained.
•TestSuite – This is combination of functional tests and logical blocks
•Testcase – Its a group that contains several test steps for the specific aspects of the service.
•Teststep – it contains the set of functional tests

•SoapUI offers us to perform AUTOMATION testing which INCLUDES functional testing, load testing and data driven testing.
•It also provides in build reporting tool and export test results log provision
•We assert our services using VARIOUS types of ASSERTIONS

•SoapUI offers us to perform automation testing which includes functional testing, load testing and data driven testing.
•It also provides in build reporting tool and export test results log provision
•We assert our services using various types of assertions

A protocol is a set of standard rules that HELPS to communicate the hardware devices through the SOFTWARE applications. There are different types of PROTOCOLS USED in the Internet and Intranet applications. They are TCP which stands for Transmission Control Protocol. It has the rules to EXCHANGE the messages between two different Internet applications. Internet Protocol uses the rules for sending and receiving the information between two different Internet addresses.Similarly, HTTP, FTP and DHCP protocols are used the set of rules to transfer the data other than Internet applications.

A protocol is a set of standard rules that helps to communicate the hardware devices through the software applications. There are different types of protocols used in the Internet and Intranet applications. They are TCP which stands for Transmission Control Protocol. It has the rules to exchange the messages between two different Internet applications. Internet Protocol uses the rules for sending and receiving the information between two different Internet addresses.Similarly, HTTP, FTP and DHCP protocols are used the set of rules to transfer the data other than Internet applications.

Envelope element is the TOP most TAG which IDENTIFIES the XML document as a SOAP message. Followed by Envelope element, you see the HEADER element that has header information. The Body element SPECIFIES the call and response information. Finally, you have a Fault element which contains errors and status information.

Envelope element is the top most tag which identifies the XML document as a SOAP message. Followed by Envelope element, you see the header element that has header information. The Body element specifies the call and response information. Finally, you have a Fault element which contains errors and status information.

Since its XML BASED, it is platform and programming language INDEPENDENT. RPC (REMOTE procedure calls) are SOMETIMES blocked by firewalls and proxy servers- Soap overcomes that.

Since its XML based, it is platform and programming language independent. RPC (Remote procedure calls) are sometimes blocked by firewalls and proxy servers- Soap overcomes that.

Generally, all the SOAP BASED web SERVICES are written by using XML language which uses standard message format that is accepted ACROSS the universe. In this format, it is easy to read, identify the errors, avoids interoperability problems etc. Here’s the sample SOAP message format.
POST /InStock HTTP/1.1
Host: localhost
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 399
SOAPAction: “http://www.example.com/soap-envelope”
<?xml version=”1.0??>
<soap:Envelope xmlns:soap=”http://www.example.com/soap-envelope”>
<soap:Header>
</soap:Header>
<soap:Body>
<m:TutorialName>SoapUI</m:TutorialName>
</soap:Body>
</soap:Envelope>

Generally, all the SOAP based web services are written by using XML language which uses standard message format that is accepted across the universe. In this format, it is easy to read, identify the errors, avoids interoperability problems etc. Here’s the sample SOAP message format.
POST /InStock HTTP/1.1
Host: localhost
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 399
SOAPAction: “http://www.example.com/soap-envelope”
<?xml version=”1.0??>
<soap:Envelope xmlns:soap=”http://www.example.com/soap-envelope”>
<soap:Header>
</soap:Header>
<soap:Body>
<m:TutorialName>SoapUI</m:TutorialName>
</soap:Body>
</soap:Envelope>

we can SENT and receive soap MSG with the HELP of HTTP, FTP or SMTP PROTOCOLS. we need to bind the soap envelope in protocol and then we can send and receive our message over the netwok.

we can sent and receive soap msg with the help of HTTP, FTP or SMTP protocols. we need to bind the soap envelope in protocol and then we can send and receive our message over the netwok.

In SOAP, PROCEDURES TAKE NAMED parameters and ORDER is irrelevant. In XML-RPC order is relevant and parameters do not have names.

In SOAP, procedures take named parameters and order is irrelevant. In XML-RPC order is relevant and parameters do not have names.

SOAP version 1.2 is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of four parts:

An envelope that defines a framework for DESCRIBING what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, a convention for REPRESENTING remote procedure calls and responses and a binding convention for exchanging messages using an underlying protocol. SOAP can POTENTIALLY be USED in combination with a variety of other protocols; however, the only bindings defined in this DOCUMENT describe how to use SOAP in combination with HTTP and the experimental HTTP Extension Framework.

SOAP version 1.2 is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of four parts:

An envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, a convention for representing remote procedure calls and responses and a binding convention for exchanging messages using an underlying protocol. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and the experimental HTTP Extension Framework.

SOAP uses an XML format to encode data. There are two WAYS in which it maps HIGH level datatypes like INTEGERS, arrays to a serialized XML format- Section 5 ENCODING and Literal encoding. Section 5 encoding, also called SOAP encoding, is named after the section in the SOAP 1.1 specification that defines it. Literal encoding on the other hand uses a XML.

SOAP uses an XML format to encode data. There are two ways in which it maps high level datatypes like integers, arrays to a serialized XML format- Section 5 encoding and Literal encoding. Section 5 encoding, also called SOAP encoding, is named after the section in the SOAP 1.1 specification that defines it. Literal encoding on the other hand uses a XML.

•  SOAP by passes all FIREWALLS thus making the process easier.
•  It has HUGE collection of protocols.
•  It is platform and LANGUAGE independent.
•  SIMPLICITY and extensible NATURE makes it the most wanted.

1. SOAP is much slower than middleware technologies.
2. Due to the USAGE of HTTP for TRANSPORTING messages and not the defined ESB or WS-Addressing interaction of parties over a message is fixed.
3.  INFORMATION regarding the usability of HTTP for different purposes is not PRESENT which makes the application protocol LEVEL problematic.

This is used to define the data types in the document. Any SOAP ELEMENT MAY use this format and it GETS IMPLEMENTED on the child and contents of the SOAP. SOAP element will never have a default encoding.

This is used to define the data types in the document. Any SOAP element may use this format and it gets implemented on the child and contents of the SOAP. SOAP element will never have a default encoding.

Some of the IMPORTANT SYNTAX rules are as follows:

1. SOAP should be coded in XML.
2.  SOAP envelope should be used for SOAP message.
3. A SOAP encoding namespace must be used by SOAP.
4. A DTD REFERENCE and a XML processing instruction should not be CONTAINED.

Some of the important syntax rules are as follows:

This attribute INDICATES whether the header is optional or mandatory for the recipient to process. If you add mustUnderstand =”1” to the child element of the header element then it STATES that the header element must be PROCESSED OTHERWISE it leads to failure.

This attribute indicates whether the header is optional or mandatory for the recipient to process. If you add mustUnderstand =”1” to the child element of the header element then it states that the header element must be processed otherwise it leads to failure.

This PART of the ELEMENT will contain the message which is intended for the ultimate delivery point. An element can be described inside the body element as a default namespace which indicates about the error message during the process. SOAP element ACTS just like a code to be processed during the execution of a CERTAIN application.

This part of the element will contain the message which is intended for the ultimate delivery point. An element can be described inside the body element as a default namespace which indicates about the error message during the process. SOAP element acts just like a code to be processed during the execution of a certain application.

A SOAP message has to travel a very long distance between its client and server but during the PROCESS a part of the message may be INTENDED to be DEPLOYED to another destination which is made possible by the SOAP elements actor attribute which address the header ELEMENT to a particular LOCATION.

A SOAP message has to travel a very long distance between its client and server but during the process a part of the message may be intended to be deployed to another destination which is made possible by the SOAP elements actor attribute which address the header element to a particular location.

A SOAP message will have the SOAP ELEMENT as the root element. SOAP element NAME SPACE should always have the VALUE as that defines the Envelope.

A SOAP message will have the SOAP element as the root element. SOAP element name space should always have the value as that defines the Envelope.

FOLLOWING ELEMENTS are contained in the SOAP message.

1. An envelope element which identifies and translates the XML document into a SOAP message.
2.  A header element is a must as it should contain header message.
3.  A body is required which should contain call and response message.
4.  Fault element is required which can communicate about the errors OCCURRED during the PROCESS.

Following elements are contained in the SOAP message.

An important difference between Remote call procedure and LOCAL call is that remote call can fail often and this occurs without the KNOWLEDGE of the user. Local CALLS are EASILY handled. Another main difficulty lies with the code writing capability because it is written in a low level LANGUAGE.

An important difference between Remote call procedure and local call is that remote call can fail often and this occurs without the knowledge of the user. Local calls are easily handled. Another main difficulty lies with the code writing capability because it is written in a low level language.

XML is chosen as a standard FORMAT because it was already in use by many large companies and immensely due to its open SOURCE nature. A wide variety of TOOLS are available on shelves which ease the process of transition to SOAP. XML can SIGNIFICANTLY reduce the speed and efficiency but binary XML is being considered as a format for future.

XML is chosen as a standard format because it was already in use by many large companies and immensely due to its open source nature. A wide variety of tools are available on shelves which ease the process of transition to SOAP. XML can significantly reduce the speed and efficiency but binary XML is being considered as a format for future.

HTTPS is similar to HTTP but it has an additional layer underneath the internet application layer which makes the DATA ENCRYPTED. This protocol is widely used than IOP or DCOM because those protocols are filtered by FIREWALLS. HTTPS protocol advocates WS-I method to provide security for transmission of secured data.

HTTPS is similar to HTTP but it has an additional layer underneath the internet application layer which makes the data encrypted. This protocol is widely used than IOP or DCOM because those protocols are filtered by firewalls. HTTPS protocol advocates WS-I method to provide security for transmission of secured data.

INTERNET application layer is used to transfer messages from one END to another end. Various products have been transported successfully from one end to another end using SOAP. Both SMTP and HTTP are two successful transport protocols used in transmitting information, but HTTP has GAINED GOOD GROUND than HTTP.

Internet application layer is used to transfer messages from one end to another end. Various products have been transported successfully from one end to another end using SOAP. Both SMTP and HTTP are two successful transport protocols used in transmitting information, but HTTP has gained good ground than HTTP.

Remote call PROCEDURE is considered as a very important FUNCTION in SOAP. In RCP a user (node) SENDS a request to another node (server) where the information is processes and sent to the user. It IMMEDIATELY sends message across the network.

Remote call procedure is considered as a very important function in SOAP. In RCP a user (node) sends a request to another node (server) where the information is processes and sent to the user. It immediately sends message across the network.

Consider a real ESTATE database with huge data ranges. If a user wants to search about a particular term, the message with all the required features such as price, availability, place, ETC will be returned to the user in an XML formatted DOCUMENT which the user can integrate into third PARTY site for additional performance.

Consider a real estate database with huge data ranges. If a user wants to search about a particular term, the message with all the required features such as price, availability, place, etc will be returned to the user in an XML formatted document which the user can integrate into third party site for additional performance.

SOAP acts as a MEDIUM to provide basic messaging FRAMEWORK. On these basic messaging frameworks abstract LAYERS are built. It transfers messages across the board in different protocols; it ALSO acts as a medium to TRANSMIT XML based messages over the network.

SOAP acts as a medium to provide basic messaging framework. On these basic messaging frameworks abstract layers are built. It transfers messages across the board in different protocols; it also acts as a medium to transmit XML based messages over the network.

SOAP acts as a MEDIUM to provide BASIC messaging framework. On these basic messaging FRAMEWORKS abstract LAYERS are built. It transfers MESSAGES across the board in different protocols; it also acts as a medium to transmit XML based messages over the network.

SOAP acts as a medium to provide basic messaging framework. On these basic messaging frameworks abstract layers are built. It transfers messages across the board in different protocols; it also acts as a medium to transmit XML based messages over the network.