open-telemetry / open-telemetry/opentelemetry-java-contrib
Cucumber-jvm instrumentation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 269
- Forks
- 196
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 38
Description
I was wondering if this repository would be appropriate for an instrumentation of cucumber-jvm.
Some similar exists on the equivalent node repository: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/instrumentation-cucumber
And the hosting of this feature in the cucumber-jvm repository has been declined: https://github.com/cucumber/cucumber-jvm/pull/2789
I'm willing to contribute and finalize the initial work made by deejgregor in the linked PR.
The alternative is for me to create my own github repository and publish the artifact on maven central, but I'm wondering if it would not be better hosted here.
Contributor 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.
Research direction
Start by reviewing the initial cucumber-jvm instrumentation work referenced in the issue and compare it with the OpenTelemetry Java contrib repository structure. Use the equivalent Node instrumentation as a reference for expected scope. Done means deciding whether this repository should host the instrumentation and, if accepted, finalizing the contribution for publication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100