Conformance Test
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing-qa
Research direction
Start by locating the repository's Kubernetes setup and conformance-test entry points. Define the scripts needed to create a cluster, run the conformance tests, and trigger them; the work is done when all three checklist items can be executed successfully.
Written by the indexing model from the issue text.
Description
- Scripts to setup kubernetes cluster
- Scripts to run conformance tests
- Trigger conformance test.
- Dominant language
- Go
- Stars
- 104
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from volcengine/cello
-
Cello CICDOpen
Difficulty 4/5 3-5 days Newbie friendliness 20/100
volcengine/cello#3 ·
All issues in volcengine/cello
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
duplication
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openvibely/openvibely#1443 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
canonical/service-mesh#845 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
keyxmakerx/Chronicle#1179 ·
Maintainers usually reply within 1 day