dapr / dapr/components-contrib
Make our conformance test framework available as a standalone library
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Developers building pluggable components have the desire to make sure that they behave correctly and are aligned with the other Dapr components.
In this repo, conformance tests are the primary way we ensure that components behave consistently and we test a baseline set of features.
We should consider making our conformance test framework available as a standalone library, which can be imported in third-party repos by developers who want to test their components using the same framework. This doesn't necessarily require splitting the tests into a separate repo, but it does require at least ensuring that the tests can be imported by another repo and used regardless of our GitHub Actions infrastructure (e.g. we need to provide a way to pass secrets to components).
Contributor guide
Research direction
Start by locating the conformance tests in the dapr/components-contrib repository and tracing their dependency on GitHub Actions and component secrets. Determine how a third-party repository could import and run the framework independently, with a documented way to provide secrets; done means an external component repository can execute the same baseline conformance tests without this repository’s CI infrastructure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100