Check acceptance criteria in a code review
Acceptance criteria checks are only available to users on a Rovo Dev Standard plan.
The pull request author’s Rovo Dev Standard plan must be on the Jira site connected to the Bitbucket workspace or GitHub organization the pull request is created in.
Rovo Dev can compare the code in your pull request to requirements listed in your linked Jira work items.
Rovo Dev will let you know whether the acceptance criteria it has found:
Are successfully met.
Are missing from the code.
Need manual checking.
Writing acceptance criteria
Where to write acceptance criteria
Rovo Dev will check for acceptance criteria in the summary, description, and custom fields of work items linked to the pull request.
Rovo Dev will find acceptance criteria in the work item description, or in custom fields labelled:
"Acceptance Criteria", "AC", or "ACs".
"Business Requirements", "Functional Requirements", or "Requirements".
"Definition of Done" or "DoD".
Rovo Dev won’t search work items for acceptance criteria if the work item description is empty (even if there are acceptance criteria in custom fields or the work item summary).
Writing tips
Rovo Dev works best with acceptance criteria that are:
Short and focused on one specific thing.
Written in clear, unambiguous language.
Describing success in measurable, positive terms.
Once you find a format and structure that works for your team, use it as a template so you can quickly reuse it for all your work items.
How Rovo Dev checks the correct work item
To find acceptance criteria for your pull request, Rovo Dev looks for a work item by checking your branch name for work item keys (e.g. ABC-1234).
If there’s no work item key in the branch name, Rovo Dev will check commit messages for a work item key (but if more than one work item key is found in commit messages, Rovo Dev will not use them).
For best results, link your pull request to one Jira work item by adding its work item key to the branch name.
Enable or disable acceptance criteria checks
In Bitbucket
To turn acceptance criteria checks off or on for your Bitbucket repository:
Acceptance criteria checks for code reviews are enabled in Bitbucket by default. Bitbucket repository admin permissions are required to turn off acceptance criteria checks.
Go to repository settings for your repository.
Select Rovo Dev code reviews from the side panel.
Toggle Acceptance criteria check on or off.
In GitHub
App admin permissions are required to turn off acceptance criteria checks on GitHub repositories.
From the app switcher (), select Rovo Dev.
From the sidebar, select Settings.
Select Manage GitHub settings.
For the organization your repository is in, select Manage organization.
For your repository, select Manage settings.
Toggle Acceptance criteria check on or off.
この内容はお役に立ちましたか?