Skip to content

Test the End-to-End Application

Key Lesson: A final regression test should follow one fresh Process instance across every role handoff, state update, named route, and completion boundary.

This final regression-style verification confirms that the complete purchasing workflow works as one continuous journey. It does not add or change any application configuration.

Create request → Submit → Approve Request → Reject → Update Request → Resubmit → Approve Request → Approve → Request Quotations → Add RFQ → Submit RFQs → Process completes

Attention

The Requester, Approver, and Procurement test users must already be assigned to their corresponding roles by the application owner or administrator. Start a fresh Process instance for this test, especially after changing task or Process configuration; existing tasks can retain the configuration that was active when they were created.

1. Create and submit a new purchase request

Section titled “1. Create and submit a new purchase request”
  1. Run the Purchasing application as the Requester test user.
  2. Open Purchase Request → Create New.
  3. Select a Cost Center, add at least one item, and enter values that you can identify throughout the test.
  4. Select Submit Request.
  5. On Home, confirm that Approve PR is available to the Approver test user.
Expected result:

Submit Request starts a fresh PurchaseRequestProcessing instance with the new request and creates Approve PR.

If this does not happen:
  • If the Process does not start, repeat Verify Approve Request with a new purchase request.

  • If Approve PR is unavailable, ask the application owner or administrator to verify the Approver test user’s role membership.

  1. Open Approve PR as the Approver test user.
  2. Select Assign Task To Myself if the action appears.
  3. Confirm that PurchaseRequestApprove displays the submitted request values and that the request fields are read-only.
  4. Enter a distinctive rejection reason in Approver comment.
  5. Select Reject.
  6. Return to Home and confirm that Revise PR is available to the Requester test user.
Expected result:

Reject completes Approve PR, and the reject route moves the same Process instance to Revise PR.

If this does not happen:

If Revise PR is not created, compare the Approve PR output handler and reject route with Connect Update Request to the Process.

3. Verify, update, and resubmit the rejected request

Section titled “3. Verify, update, and resubmit the rejected request”
  1. Open Revise PR as the Requester test user.
  2. Select Assign Task To Myself if the action appears.
  3. Confirm that PurchaseRequestUpdate displays the submitted request data and the distinctive rejection comment.
  4. Confirm that the request fields are editable and the rejection comment is read-only.
  5. Change one or more request values so that you can identify the revision.
  6. Select Resubmit.
  7. Return to Home and confirm that the same Process instance has created another Approve PR task.
Expected result:

Resubmit completes Revise PR, updates process.request, and follows the resubmit route back to Approve PR without starting another Process instance.

If this does not happen:
  • If the rejection comment is missing, confirm that the prior Approve PR handler stored data.comment in process.request.comment.

  • If the Process does not return to Approve PR, repeat Verify Reject and Resubmit with a fresh Process instance.

  1. Open the new Approve PR task as the Approver test user.
  2. Select Assign Task To Myself if the action appears.
  3. Confirm that the Screen displays the revised request values.
  4. Optionally enter an approval comment, then select Approve.
  5. Return to Home and confirm that Request Quotation from Vendors is available to the Procurement test user.
Expected result:

Approve completes Approve PR, and the approve route moves the same Process instance to Request Quotation from Vendors.

If this does not happen:

If the revised values do not appear or the Procurement task is not created, confirm the revision loop and approval route in Verify Reject and Resubmit and Connect Request Quotations to the Process.

  1. Open Request Quotation from Vendors as the Procurement test user.
  2. Select Assign Task To Myself if the action appears.
  3. Confirm that PurchaseQuotationCreate displays the revised, approved purchase request and that the request fields are read-only.
  4. Select Add RFQ.
  5. Enter a vendor name in the new vendor-level Quotation entry and confirm that the value remains visible.
Expected result:

PurchaseQuotationCreate receives the current process.request and adds a vendor-level This.Quotation entry to screen.request.quotations.

If this does not happen:

If the request or Quotation entry is incorrect, repeat Verify Procurement with a fresh Process instance.

6. Submit RFQs and verify Process completion

Section titled “6. Submit RFQs and verify Process completion”
  1. Select Submit RFQs.
  2. Return to Home.
  3. Confirm that Request Quotation from Vendors is no longer active.
  4. Confirm that the sendRequest route has reached the End Event and the Process has completed.
Expected result:

Submit RFQs completes the Procurement task. Its output handler returns sendRequest, the matching route reaches the End Event, and the PurchaseRequestProcessing instance completes.

If this does not happen:
  • If the task does not submit, confirm that Submit RFQs runs await output.submit(screen.request).

  • If the task submits but the Process does not complete, confirm that the User Task output handler returns sendRequest and that its outgoing route to the End Event is also named sendRequest. For exact matching behavior, see Process Routes.

Use this final checklist to confirm the cross-stage behavior that is only visible after the complete journey succeeds.