Document guidelines on testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- documentation, testing-qa
Research direction
Start by reviewing the proposal copied from issue #122 and inspect the existing analyzer unit and smoke tests to identify current coverage and conventions. Define concrete testing guidelines for analyzed and unanalyzed exercises, then document them and verify that the guidance matches the repository's existing tests.
Written by the indexing model from the issue text.
Description
I think we should come up with some guidelines on how analyzers should be tested. My proposal would be:
- Unit tests should exist to obtain as much code coverage as possible. Correctness of each exercise analyzer should be tested that way.
- Each exercise should have at least two smoke tests: one with an optimal solution that receives no feedback, and one with a solution that receives at least one exercise-specific comment.
- Next to that, a few smoke tests to cover exercises for which no analyzer is implemented should be present too, to make sure the analyzer works properly for every exercise. By that I mean that it shouldn't crash or something.
Once we come up with some concrete guidelines, we should probably write them down in the docs.
Originally posted by @sanderploegsma in https://github.com/exercism/java-analyzer/issues/122#issuecomment-1924524027
- Dominant language
- Java
- Stars
- 13
- Forks
- 27
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 7
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.
More from exercism/java-analyzer
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
exercism/java-analyzer#298 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
exercism/java-analyzer#271 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
exercism/java-analyzer#227 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
exercism/java-analyzer#218 · 3 comments ·
-
x:size/small
exercism/java-analyzer#176 · 1 comment · 1 assignee ·
All issues in exercism/java-analyzer
Similar issues
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Needs: Triage Type: Feature request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AntennaPod/AntennaPod#8794 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2760 ·