Automated Test Framework use case: test a Service Catalog request

This use case illustrates testing a service catalog request with the Automated Test Framework.

Before you begin

Role required: atf_test_admin

About this task

With the Replay Request Item test step, you can test the service catalog ordering process once a request exists and has a record in the request item table. In the Australia release, you cannot create an automated test for the process by which the user creates a new request.

Procedure

1. Replay an existing service catalog request item.

   This test step inserts a new record in the [sc_request] table for the catalog request item RITM0010001.

This insertion triggers the Service Catalog Request workflow, which checks the price of the item, determines that it exceeds $1000.00, and therefore generates approval records for users belonging to the Catalog Request Approvals group. In this example, only one user– Eric Schroeder – belongs to this group.

1. Impersonate Eric Schroeder, the user who needs to approve this Service Catalog Request.

1. Verify that the system created an approval record for Eric Schroeder and this request.

   Note that for the Approval for field, you assign the output value from Step 1.

1. Set the state of this approval record to Approved.

The Service Catalog Request workflow sees that all required approval records have the state of Approved and transitions to the Approval Action which marks the request record \[sc\_request\] as Approved.

When the record in \[sc\_request\] changes to the Approved state, an associated business rule generates request items \[sc\_request\_item\] for each item in the request. In this example, the request contains only one item, so the business rule inserts one record into the \[sc\_request\_item\] table. This insertion triggers the Service Catalog Item Request workflow.

The first activity in the Service Catalog Item Request workflow generates an approval record for the head of the department in which the requesting user works. In this example, the department head is Natasha Ingram.

1. The workflow does not continue until the department head approves it, so the next test step impersonates Natasha Ingram.

1. Obtain the sys_id for the new approval record with the Record Query step.

   Note that Record Query creates an output variable with the sys_id of the first record returned from the query.

1. Set the approval record to Approved.

Note how Step 7 refers to the **First record**output variable from Step 6 to specify which record to approve. When the record is approved, the workflow transitions to the next Approval - User activity, which generates an approval record for the CIO. In this example, the CIO is Bow Ruggeri.

1. Impersonate Bow Ruggeri.

2. Obtain the sys_id for the approval record for Bow Ruggeri.

3. Set the approval record to Approved.

   When the record is approved, the workflow transitions to the Approval Action activity which sets the record for this item in the [sc_request_item] table to Approved. The workflow transitions to the Catalog Task activity labelled Asset Mgmt. Fulfills Order. This Catalog Task activity generates a new record in the [sc_task] table that instructs a user in the Fulfillment group to order the item.

1. Impersonate a user in the Fulfillment group, in this example ATF.User.

1. Obtain the sys_id for the new catalog task with the Record Query step.

   Note that Record Query creates an output variable with the sys_id of the first record returned from the query.

1. Mark the [sc_task] record as Closed Complete.

Note how Step 13 uses the **First record**output variable from Step 12 to specify which record to mark as **Closed Complete**.

When the record is marked **Closed Complete**, the workflow exits the Catalog Task activity along the In Stock exit path.

The workflow transitions to the Notification activity, then to the Catalog Task activity labelled Deploy Item to User.The Deploy Item to User Catalog Task activity inserts a new record into the \[sc\_task\] table that instructs a user in the Deployment group to deliver the item.

1. Obtain the sys_id for the new catalog task with the Record Query step.

   Note that Record Query returns an output variable with the sys_id of the first record returned from the query.

1. Mark the [sc_task] record as Closed Complete.

   Note how Step 15 uses the First recordoutput variable from Step 14 to specify which record to mark as Closed Complete.

When the record is marked Closed Complete, the workflow exits the Catalog Task activity, logs a message, and exits.

1. Verify that the request item in [sc_request_item] has the state Closed Complete.

1. Verify that the request [sc_request] has the state Closed Complete.

Parent Topic:Automated Test Framework use case examples

Related topics

Replay Request Item