Create and run a REST service API test

This lesson describes how to create and run a REST service API test, using a prototype model of the service in OpenText Functional Testing.

Create a REST service test

Add a REST service test to your MyFlight Application solution to test the Web (API) of the MyFlights app.

Create the API test:

  1. Start with OpenText Functional Testing and the MyFlight Application solution open.

    For more details, see Start OpenText Functional Testing and create a solution.

  2. Select the New dropdown in the toolbar, and then select New Test.

  3. In the New Test dialog:

    • Select API Test.
    • In the Name field, enter MyFlightRESTService.
    • In the Location field, ensure that the test is saved in the C:%HOMEPATH%\UFT One directory.

    Click Create to add the test to your solution.

  4. Continue with Create a REST service structure.

Back to top

Create a REST service structure

This exercise describes how to create a model in OpenText Functional Testing of your rest methods and properties, for OpenText Functional Testing to use in test steps when testing the REST service performance.

This section includes the following parts: 

Create a service, resource, and method

  1. Start the Flight API app. For details, see Flight API layer.

    Note: Keep the OpenText Flights Service APIs dialog open while performing this lesson to ensure that the Flights API service is running while OpenText Functional Testing runs the test.

  2. In the OpenText Flights Service APIs dialog, click Help to display a browser window with all method details.

  3. In OpenText Functional Testing, click the Add REST Service toolbar button.

  4. In the Add REST Service dialog:

    • Replace the New Service name with Flights REST Service.
    • Click the Add Resource toolbar button .

    A new Resource node is added to the tree. Change the name of this resource to FlightOrders.

  5. Still in the Add REST Service dialog, click the Add Method toolbar button .

    A new Method node is added to the tree. Change this method name to ReserveOrder.

  6. Continue with Configure the REST service method model URL.

Configure the REST service method model URL

Provide OpenText Functional Testing with the application's service URL, at the service, resource, and method levels:

  1. Still in the Add REST Service dialog, select the Flights REST Service node in the tree.

  2. In the General tab on the right, define the URL property value as:

    http://localhost:8000

  3. Select the FlightOrders node in the tree on the left. Notice that the URL you just entered is shown as the URL value here.

    In the General tab on the right, define the Relative URL property value as:

    Flights_REST

  4. Continue with Add request information for the ReserveOrder method model.

Add request information for the ReserveOrder method model

Define property values for the ReserveOrder method:

  1. Still in the Add REST Service dialog, select the ReserveOrder node in the tree on the left.

  2. On the right, click the HTTP Input/Checkpoints tab tab, and define the following property values:

    Relative URL /FlightOrders
    HTTP method POST

  3. Click the HTTP tab on the right, and do the following:

    • From both the Request Body and Response Body dropdowns, select XML.

    • In the Request Body text editor area, enter the following code:

      <FlightOrderDetails xmlns="HP.SOAQ.SampleApp">
  <Class>Business</Class>
  <CustomerName>John Parker</CustomerName>
  <DepartureDate>2115-02-28</DepartureDate>
  <FlightNumber>3233</FlightNumber>
  <NumberOfTickets>1</NumberOfTickets>
  </FlightOrderDetails>

      Click to view the properties you entered in a grid view.

  4. Click the HTTP Input/Checkpoints tab again.

  5. In the Input area, scroll down to and expand the Request Headers > Request Headers [1] nodes.

    Note the settings for this response, as you'll need them for subsequent steps.

  6. Continue with Create output properties for the ReserveOrder method model.

Create output properties for the ReserveOrder method model

  1. Still in the Add REST Service dialog, with the ReserveOrder node selected in the tree on the left, select the Custom Input/Checkpoints tab on the right.

  2. Click Add > Add Output Property.

  3. In the Add Output Property dialog, enter the following values:

    • Name. Total_Price
    • Type. Int

    Click OK to add the property.

  4. Repeat the previous step to add another output property, named Order_Number, of type Int.

  5. Continue with Test the ReserveOrder method model.

Test the ReserveOrder method model

Test the model you created in the previous steps before you finish adding it to your test:

  1. In the Add Rest Service dialog box, with the ReserveOrder method node selected on the left, click the Run Method toolbar button.

    You may need to expand the left pane to see it.

    OpenText Functional Testing runs the method to test it, and displays the results at the bottom of the Add REST Service dialog.

    For example:

  2. Click OK to add the service model you've created to the Toolbox.
  3. Continue with Add methods to your REST API test.

Back to top

Add methods to your REST API test

Add the methods you created in the REST service model above to your REST API test.

Import the data source, then add a step, linked to the data source, and a checkpoint on that step.

Import a data source to your test:

  1. Import a data source to use in your test. In the Data pane (View > Data), click New Data source and select Excel.

  2. In the New Excel Data Source dialog, in the Data Source name field, enter Flights_REST.

  3. Browse to and select the Excel file saved in the <Installdir>\samples\Flights Application directory.

  4. Select Link to the Excel file in its original location, and click OK to add the data in the Excel file to your test.

  5. Continue with Add a step and link its properties to the data source:.

Add a step and link its properties to the data source:

  1. From the Toolbox pane, expand the Local Activities > Flights REST Service node, and drag the ReserveOrder step to the canvas.

  2. Select the ReserveOrder step in the canvas to display the Properties pane.

  3. Click the HTTP tab on the right.

    Click the Grid button, and define the following values, using values from the Data source column:

    • Class
    • CustomerName
    • DepartureDate
    • FlightNumber
    • NumberofTickets

    For each property, do the following;

    1. Click or hover in the Value cell and click Link to a data source .
    2. In the Select Link Source dialog, select Data source column, and then select the Flights_REST! input node on the left.
    3. On the right, select the relevant column for the property you are parameterizing.
  4. Continue with Set a checkpoint for the ReserveOrder step.

Set a checkpoint for the ReserveOrder step

Add a checkpoint to your test to verify the API response value:

  1. Select the ReserveOrder step in the canvas to display the Properties pane, and then select the HTTP tab .

  2. Save the following code to a file named response.xml on your OpenText Functional Testing machine:

    <?xml version="1.0"?>
<CreatedOrderParams xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="HP.SOAQ.SampleApp">
	<OrderNumber>93</OrderNumber> 
	<TotalPrice>374.400024</TotalPrice> 
</CreatedOrderParams>

  3. In the HTTP tab , in the Response area at the bottom, ensure that XML is selected as the Response Body.

  4. Click , and browse to and select the response.xml file you just created.

    OpenText Functional Testing loads the XML schema.

  5. In the new schema loaded, update the following values:

    OrderNumber > 10
    TotalPrice < 500
  6. Continue with Run the REST service test.

Back to top

Run the REST service test

Run the test you created in the previous exercises and view the run results:

  1. Ensure that the Flight API app is still running. For more details, see Analyze your application.

  2. Define the number of test iterations. In the canvas, select the Test Flow box.

  3. In the Input tab on the Properties pane:

    • Select the 'For' Loop option.
    • In the Number of Iterations field, enter 8.

  4. Configure how OpenText Functional Testing handles your data during a test run:

    1. In the canvas, select the Test Flow box to display the Properties pane for the test flow.

    2. In the Properties pane, select the Data Sources tab .

    3. Select the Flights_REST!Input entry in the table and click Edit.

    4. In the Data Navigation dialog, specify the data navigation details as follows:

      Start at: First row
      Move by: 1 rows Forward
      End at: Last row
      Upon reaching the last row Wrap around

    5. Click OK, and save your test.

  5. Click the Run toolbar button .

    Ensure that the MyFlightRESTService test is selected, and then click Run to run your test.

  6. When the test is complete and the run results are shown, navigate down in the Test Flow and select any of the ReserveOrder nodes.

    In the Captured Data area on the right, view the Request and Response data generated during the test run.

    • Click any of the links in the table to view the full request or response code.

      For example:

    • Scroll all the way down to view the checkpoint data.

      In this case, one of the checkpoints failed because there was a price included that was larger than 500.

  7. Continue with Resolve a REST service conflict.

Back to top

Resolve a REST service conflict

Resolve a REST service conflict if the service model's properties changed after you created the test.

In this exercise, you create a conflict and then use OpenText Functional Testing's Resolve Conflict wizard to update your test.

Create a conflict in your REST service

Edit the service model properties to create a conflict in your test, when compared to the updated service model:

  1. In the Toolbox pane, right-click the Local Activities > Flights REST Service node, and select Edit Service.

  2. In the Edit REST Service dialog, select the ReserveOrder node.

  3. On the right, select the Custom Input/Checkpoints tab .

  4. Select the Total_Price property, and then click the Edit Property button at the top.

  5. Change the name to TotalPrice (remove the underscore between the words).

  6. Repeat the previous steps to change the Order_Number property name to OrderNumber.

  7. Click OK to make the change to your service and close the dialog box.

    OpenText Functional Testing saves the changes, and now shows an alert in the canvas, indicating that the values no longer match.

  8. Continue with Resolve the conflict you created.

Resolve the conflict you created

Now that you have a conflict between your test and your API service model, resolve it to update your test with the new values:

  1. Click the alert in the canvas to display its details, and then click on the alert text to open the Resolve REST Conflicts wizard.

  2. In the first screen (Select Steps), select the checkbox for the ReserveOrder step, and click Next.

  3. The Resolve Conflicts screen in the wizard highlights all steps with conflicts in red.

    In the Output Properties area at the bottom, in the After changes box, select the Total_Price property.

  4. Click the Remove button between the Before.. and After.. boxes to remove the Total_Price property.

  5. Repeat these steps to remove the Order_Number property too.

  6. Click Next. The Finish screen should confirm that you have successfully removed all conflicts.

  7. Click Finish to exit the wizard, and confirm that the alert was removed from the canvas.

    The property names in the test have now been updated to reflect the new name in the service model.

  8. Save your test, and continue with other lessons in the tutorial.

Back to top

Next steps: