Project proposal applying to move Aries Agent Test Harness to OWF as the OWL project #44
Conversation
Signed-off-by: Stephen Curran <swcurran@gmail.com>
swcurran
requested review from
tkuhrt,
rolsonquadras,
wenjing,
skounis,
petecool,
davidz25 and
aceshim
as code owners
Signed-off-by: Stephen Curran <swcurran@gmail.com>
projects/agent-test-harness.md
Outdated
|
|
||
| ## Preferred Maturity Level | ||
|
|
||
| We propose that the project be at the “Growth” level. All three of the components have been used extensively in the past and are well documented. Many groups have used the tools in testing their own instances of the various support agents and wallets. As we move the project to OWF and start up the Wallet Interoperability Special Interest Group (link to PR to be added) these tools will be useful in enabling testing across frameworks and deployments built on those deployments. We look to expand their use in both the scope of the testing they enable, and their use by the community. |
There was a problem hiding this comment.
Can you comment on how the project meets each of the "Growth" acceptance criteria outlined in the project lifecycle?
There was a problem hiding this comment.
Added how the Growth stage requirements are met to the proposal.
projects/agent-test-harness.md
Outdated
| * Automation: The Agent Test Harness automates the testing of agents, making it easier for developers to continuously verify the compliance and performance of their implementations. Developers can configure what agent implementations with whom they want to test interoperability and for each, what specific tests they want executed. Implementations can even include their CI pipelines select Agent Test Harness interoperability tests. | ||
| * Extensibility: The framework is highly extensible, allowing developers to add their implementations for testing and to construct custom tests and scenarios that suit a wide variety of use cases. This flexibility is important for testing a wide range of decentralized identity solutions across different industries. | ||
| * Comprehensive Coverage: The test harness covers a wide array of functionalities that decentralized trust agents should support, including secure messaging, protocols, and credential issuance, verification and revocation across a range of credential formats. | ||
| * Community-Driven: Agent Test Harness is intended to be developed and maintained by a global community of contributors to ensure that it stays up-to-date with the latest standards and best practices in the decentralized identity space. |
There was a problem hiding this comment.
It would be interesting to see what might be done with some of the labs that we have that would allow us to add sd-jwt interoperability testing to this project (if it does not already exist).
projects/agent-test-harness.md
Outdated
| * Comprehensive Coverage: The test harness covers a wide array of functionalities that decentralized trust agents should support, including secure messaging, protocols, and credential issuance, verification and revocation across a range of credential formats. | ||
| * Community-Driven: Agent Test Harness is intended to be developed and maintained by a global community of contributors to ensure that it stays up-to-date with the latest standards and best practices in the decentralized identity space. | ||
|
|
||
| As mentioned in the [Project Name](#project-name-to-be-determined) section, we suggest that Agent Test Harness be combined into a single project with the Mobile Wallet Test Harness and Akrida load testing tool. All will be separate repos in the project, but share common project components (governance, meetings, Discord community, etc.). |
There was a problem hiding this comment.
Ideally for consistency with previous OWF decisions, we could then make each repo have the same project prefix (e.g., project-name-repo-name).
projects/agent-test-harness.md
Outdated
|
|
||
| ## Proposed Project Governance | ||
|
|
||
| The current governance model under Hyperledger is consensus-based. This means that decisions are made through discussions, with the aim of community consensus, as outlined in the [Aries Project Charter](https://docs.google.com/document/d/1F6RbR7xDaBt5CDJhqLJzR4c1pDJtyPGshp9fy6eVtSM/edit?usp=sharing). In cases where no clear consensus is established, a project Technical Steering Committee, or the maintainers (those with escalated GitHub privileges) are granted a louder voice. This approach has proven effective. |
There was a problem hiding this comment.
Is the intention for this project to be distinct from the other Aries proposals and their governance processes when it moves to OWF?
There was a problem hiding this comment.
Agent Test is proposed to be a separate project at OWF, independent of the other artifacts stemming from the existing Hyperledger Aries project, with separate governance. That reflects the distinct purpose of the project (and its sub-projects), and community around it.
Signed-off-by: Stephen Curran <swcurran@gmail.com>
|
We support this project at GAN and will be actively contributing shortly. |
Signed-off-by: Stephen Curran <swcurran@gmail.com>
…all three tools Signed-off-by: Stephen Curran <swcurran@gmail.com>
Signed-off-by: Stephen Curran <swcurran@gmail.com>
swcurran
changed the title
|
Updated the project name and the project proposal file name. Adjusted the wording when referring to the overall project (OWL) and the entire toolset vs. sections talking about the individual tools -- Agent Test Harness, Akrida, and Mobile Wallet Test Harness. |
A project proposal applying to move a component of Hyperledger Aries -- Aries Agent Test Harness -- to OWF.
Agent Test Harness is an extensible open-source testing framework designed to validate the functionality and interoperability of agents and components within the decentralized trust ecosystem. A summary of its daily interoperability test runs are published on the website https://aries-interop.info. The test harness is crucial for ensuring that different decentralized trust agent implementations, which are responsible for handling decentralized identifiers (DIDs) and exchanging verifiable credentials, can interoperate seamlessly. Agent Test Harness currently includes support for the OWF’s Credo-TS project, and is used by the OWF’s Mobile Agent Test Harness project. The proposal also includes moving into the same project Aries Akrida, a scriptable tool for generating loads to apply to Aries (and potential, other) wallets/agents.
@nodlesh, @TelegramSam, @tkuhrt, @KimEbert42 @TimoGlastra @ianco
This PR is associated with #42.