January 10th, 2022 by inflectra
We had a customer ask us what was the recommended way to manage the Acceptance Criteria of requirements in a project. There are actually several different ways you can handle acceptance criteria depending on your exact process (and preference):
We discuss each of these options below:
First, imagine you have the following user story that you want to write acceptance criteria for:
As a writer, I want to receive notifications when others add comments so that I am up-to-date.
In Spira you will represent this as a requirement of type user story:
Now you want to add the acceptance criteria to the user story. Here's some different ways you can write the user story:
The simplest option is to just add a custom Rich Text property to the User Story requirement artifact:
That will appear underneath the main description:
Another option would be to use a separate requirement to store the acceptance criteria. You can use a requirement of type Acceptance Criteria and make it a 'Has Steps' type so that you could enter the acceptance checklist as steps.
Then you can enter in the Acceptance Criteria into this requirement as steps:
You can then link to the user story using the Associations feature:
You can also see the relationship in the mind-map view:
Another option is to create a .Feature file in the Documents section and link to the requirement as an Attachment:
That way you get the automated Gherkin BDD syntax highlighting:
You can now link this to the requirement as an attachment:
Finally, you can use a test case of type Acceptance Criteria and use the test steps to reflect the acceptance criteria:
Then the Test Coverage tab is used to link this test case to the original user story:
And if you have any questions, please email or call us at +1 (202) 558-6885
Are you looking for a platform that helps you deliver better software, faster?