nelsonic / nelsonic/github-scraper
Should we check repos for automated testing?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 456
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
Could we for example check that a repo has a test folder?
This is not fool-proof as not everyone who has tests will have a test folder (even though it's the convention) and having one doesn't mean you actually have any tests, much less guarantee coverage. But would checking for something like this be an interesting initial indicator of tested code?
(Aside: I think looking for badges would prove relatively inconclusive (e.g. if trying to look for test coverage details) because they're still not used widely enough)
Contributor guide
No contributing guide indexed for this repository
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
No source file, test, or entry point is named in the issue. First review the repository's existing GitHub page-scraping indicators and decide how a test-directory signal would fit; done would require an agreed detection scope and implementation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100