Explore topic-wise InterviewSolutions in .

• Create a project and include the WSDL i.e. Web Service Description Language file in the project.
• Add custom programming utilizing GROOVY steps by first adding TEST SUITES followed by test cases and test steps.
• If an external DATA source is used add assertions.
• Then RUN.

An assertion in SOAPUI is USED to validate the responses and whether the data meets the DESIRED expectation. After you received the response to a REQUEST, FOLLOW these steps-

• Create a project and ADD the Web Services Description Language.
• Add Test Suite followed by a Test case and a set of Test Steps.
• Do the request execution.

Once the steps are done, the user can add the assertions-

• Navigate to the top of log tabs and Click>Add Assertions.
• Configure them according to the data and type needed.

• First, Right-CLICK on the Test STEP node.
• Select >Add Step and Properties option from Context menu.
• Click OK once you entered the desired property name.
• For adding a property, navigate to properties screen and click > properties with groovy SCRIPT (1) icon.
• Again click OK once you entered the desired property name.
• Users can give any default value to the property.
• After that property step, a groovy script test step should be introduced.

API testing is similar to software testing except it mainly focuses on APIs. SOAPUI allows USERS to test SOAP and REST web services in the following ways-

• First Test Cases need to be developed using SOAPUI.
• By using the “Add to TestCase” BUTTON users have to make a REST Request.
• Assertions need to be added to VALIDATE the response MESSAGE.

To create a Test SUITE in SOAPUI, use the menu “NEW Test Suite” or by a particular button PRESENT on top of an array of Test Suites. To import Test Suite one of the following approaches can be chosen-

• In File Menu > Import Project option: To add an existing project.
• In File Menu > Import Preferences option: It is USED to import SOAPUI settings from another setting file.
• In File Menu > Import Remote Project Option: To import a remote project in the current workspace.
• In Icons Toolbar > Import Option: Used to import an existing SOAPUI project in the current workspace.

USER REQUIRES scripting to automate test cases in SOAPUI. In SOAPUI SCRIPTS are used as follows-

• By Groovy Script Test Step.
• Opening or closing of the project.
• Pre or post-execution of test cases for doing repetitive tasks such as memory CLEAN up or initialization.
• Using SOAPUI pro, scripting of SOAP and REST can be DONE with a single click.

To test WEB services using SOAPUI, we need to create test cases followed by these steps-

• Make a REST request from Request POPUP by clicking the “Add to Test Case “ button.
• Now, Test Steps can be added to a Test Case that can be NEW or existing.
• The next step is to add ASSERTIONS to validate the response message.

It means to store the test DATA which includes input and expected output into an external data source like Excel, Database, XML file. A LATER iteration of this data source using a respective component can be done.

Data-Driven Testing using SOAP UI-

• Open the SOAPUI editor and click on File > New > Functional Test and enter the .wsdl URL as shown in the image below-
• Click on Finish Button.
• To create a new test suite, right-click on “Project” and then click on “New Test Suite”.
• Right-click on “Test Suite” and click “New Test Case” to create a test case under that suite.
• Right-click on “Test Case” and then go to Add Step > Properties, values of defined variables are held by these properties.
• Now again Right-click on “Test Case” and click Add Step > SOAP Request.
• In Add Step > Groovy Script, the user has to PLACE the groovy script and click on the “Save” OPTION.

It is a scripting language that includes all the java LIBRARIES internally. Groovy scripts help the users to customize and allow them to add custom VALIDATIONS to SOAPUI TESTS. Inside SOAPUI, it can be used in-

• Groovy Script TEST Step
• In Script Assertion- WITHIN the test step.

• Test SUITE level default or CUSTOM properties: A user can add multiple characteristics that can be APPENDED at the test suite level and these characteristics can be utilized from any test step in any test case.
• Project level default or custom properties: A user can append any NUMBER of properties at the project level, and then they can be accessed from any test step which is under that test suite.
• Test Step level default or custom properties: Here number of properties can be ADDED to a test case at the test case level, and these properties can be utilized in any test step from that test case.