Test plan variables

Test plan variables that are available through our webhooks, designed to provide comprehensive insights into your test execution plans. These variables enable you to integrate test plan data directly into their custom applications, reporting tools, or automation scripts. By leveraging these variables, you can access critical information such as plan status, progress, associated project details, and key metrics like the count of passed, failed, or blocked test cases. Following is a detailed list of each variable, its description, and an example of its expected value or format.

Events (Trigger conditions)

Webhooks for test plan variables are triggered when significant actions related to a test plan’s lifecycle occur. These events are crucial for synchronizing your external systems with the state and progress of your test plans. The following actions will trigger a webhook payload containing test plan variables:

• Test plans created: Triggered when a new test plan is established in the system.

• Test plans updated: Triggered when any details or attributes of an existing test plan are modified.

• Test plans completed: Triggered when a test plan reaches its Completed status.

• Test plans deleted: Triggered when a test plan is permanently removed from the system.

These test plan variables are essential for creating dynamic and responsive integrations that react to the lifecycle and progress of your testing efforts through webhooks. By incorporating these details you can automate notifications, update external dashboards, and ensure all stakeholders are informed about the state of your test plans. If you have any further questions or require additional variables, refer to our full API documentation or contact our support team.