Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Categorized Test Cases to AIP Verisons with Links on AIP RFC #3

Closed
nodlesh opened this issue Feb 5, 2020 · 0 comments
Closed

Categorized Test Cases to AIP Verisons with Links on AIP RFC #3

nodlesh opened this issue Feb 5, 2020 · 0 comments

Comments

@nodlesh
Copy link
Contributor

nodlesh commented Feb 5, 2020

AS AN Agent Builder, I WANT to know what test cases are for what part of the Aries Interop Profile RFCs, SO THAT I know what test cases to execute based on the implemented RFCs

Acceptance Criteria

Scenario: Agent Builder needs to know what tests to run for the AIP version they are working on
Given an Agent Builder who is looking at an AIP version
When they look at an AIP version in the AIP RFC
Then they will see a link to the relevant subset of Aries test cases in the Aires Test Suite

Scenario: Aries Test Harness Owner maintains links from AIP RFC version to relevant Test Cases
Given the Aries Test Harness Owner
When they have made a change to the Aries Test Suite
Then they will tag the test scenarios in the feature file with the appropriate RFC version
And they will update the links in the AIP RFC to the relevant Test Cases

@nodlesh nodlesh assigned nodlesh and unassigned nodlesh Feb 5, 2020
swcurran pushed a commit that referenced this issue Jun 2, 2020
swcurran pushed a commit that referenced this issue Sep 4, 2020
Added Test Coverage Matrix to documentation
Matt-Spence pushed a commit to Matt-Spence/aries-agent-test-harness that referenced this issue Jun 29, 2021
Added Test Coverage Matrix to documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants