To enable Test Status updates in Bitbucket Pull Requests like the ones shown below, configure an integration with Bitbucket and connect it to the test trigger.
Configure
Create an App Password on Bitbucket with "Pull Request: Write" permissions (see App passwords | Bitbucket Cloud | Atlassian Support). Copy it to your clipboard.
Bitbucket App Passwords can be managed at the following link: Bitbucket User Settings. You may revoke App Passwords at any time from Bitbucket.Create a new integration: go to Test Automation (using the left navigation bar) and select Manage Integrations from the Quick Actions menu.
On the Manage Integrations Page, select Add Bitbucket Integration from the Quick Actions menu. Enter a nickname for the configuration, your Bitbucket Organization (typically the entity in your Bitbucket URL preceding the repository name), the username of the Bitbucket User that created the App Password, and the App Password from step 1.
Please note that you will not be able to view the app password after saving it. To update, use the Edit App Integration > Edit Password form.
Note:
If you have revoked and created a new App Password, don't forget to update it in Miqa.
Connect
To add a downstream PR-update step to an existing test trigger, update the appropriate Caller Configuration.
Caller Configurations refer to the connection from the CI build trigger to Miqa. Different Caller Configurations may have different downstream actions.
Go to the Test Trigger: go to Test Automation, then Test Triggers, and then open the trigger page.
Select the Caller Configuration (e.g. CircleCI or Bitbucket Pipelines) to assign the downstream step. If needed, add a new Caller Configuration.
Select the checkbox Update Bitbucket PullRequest Status. Select the integration added in the Configure process above and save the Caller Configuration.
That's it! Test executions will now trigger the downstream steps.