Improve code coverages using different technique in analyzers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
The currently implemented package analyzers provide a limited coverage of the code when the payload is hiding in non setup/import phase
Suggesting to improve coverage with a best-effort approach to reflect and dynamically instantiate objects inside the package to increase the analysis coverage.
From my experience with this approach implemented in another similar project, I can share this is doable in a reasonable time for the following languages:
Javascript
Python
Java
Groovy
C#
Clojure
Scala
Kotlin
I'm planning to contribute it to this project, let me know WDYT
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
The issue names no files, tests, or analyzer entry points. Start by locating the package analyzers and reviewing how coverage is measured; done would require an agreed best-effort approach for dynamically instantiating objects and evidence that coverage improves for the listed languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, csharp, groovy, java, javascript, kotlin, python, scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100