The latest updates on your projects. Learn more about Vercel for Git ↗︎

Someone is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

/claim #9038

Test Plan: End-to-End Testing for Routing Forms Webhook Subscription

Objective:
The objective of this test plan is to perform end-to-end testing for the routing forms webhook subscription. The test plan includes both manual tests and automated tests to ensure comprehensive verification. The focus will be on running the e2e test using the specified command and verifying the functionality of the gotoRoutingLink function.

Test Scope:
The test scope includes executing the e2e test specifically for the webhook subscription of routing forms. The test plan will cover the functionality of the gotoRoutingLink function after its relocation to the @calcom/web/playwright/lib/testUtils module.

Test Environment:
The test environment should consist of:

The application or system where the routing forms webhook subscription is implemented.
Access to the routing forms and their webhook configuration.
Test data or content to simulate the submission of a routing form.
Test Plan:
4.1 Manual Test:

4.1.1 Manual Verification of Routing Forms Webhook Subscription:
Objective: To manually verify the functionality of the routing forms webhook subscription.
Steps:

• Identify the routing forms that are configured with webhook subscriptions.
• Generate test data or content that represents a valid submission for a routing form.
• Submit the test data through the routing form.
• Monitor the webhook endpoint or logs to confirm that the webhook is triggered.
• Verify that the expected data from the form submission is received by the webhook endpoint.

4.1.2 Manual Testing of gotoRoutingLink Function:
Objective: To manually test the gotoRoutingLink function after its relocation to the @calcom/web/playwright/lib/testUtils module.

Steps:

• Identify the test scenarios or conditions in which the gotoRoutingLink function is expected to be invoked.
• Manually trigger the gotoRoutingLink function with the appropriate parameters in each identified scenario.
• Verify that the function successfully navigates to the expected routing link.
• Confirm that the routed page or destination corresponds to the expected behavior.

4.2 Automated Test:

4.2.1 End-to-End Testing for Routing Forms Webhook Subscription:
Objective: To automate the end-to-end testing of the webhook subscription for routing forms.
Steps:

• Develop an e2e test script specifically for testing the webhook subscription functionality.
• Configure the test script to simulate the submission of a routing form with test data.
• Ensure that the test script triggers the webhook endpoint.
• Verify that the expected data from the form submission is received by the webhook endpoint.
• Implement assertions in the test script to validate the correctness of the received data.
• Execute the e2e test script using the specified command: yarn test-e2e webhook -g "FORM_SUBMITTED".
• Review the test results and ensure that all assertions pass, indicating the successful webhook subscription functionality.

Test Reporting:
For each test, document the observed results, any deviations from expected behavior, and any defects found during testing. Report and track the issues found using a bug-tracking system.

Test Completion Criteria:
The test execution is considered complete when:

• The manual verification of the webhook subscription for routing forms has been performed and documented.
• The manual testing of the gotoRoutingLink function has been executed, and the results are documented.
• The e2e test for the webhook subscription using the specified command has been executed, and the test results are documented.

The pipeline passes now.