marigold-dev / marigold-dev/deku
[Testing] Convention for test description
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Please open an issue for this, but those tests are mostly regression test, they're not trying to enforce failure properties, just to ensure that the cases that we actually care are covered here.
_Originally posted by @EduardoRFS in https://github.com/marigold-dev/deku/pull/444#discussion_r813293134_
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
Start by reading the regression-test discussion referenced from PR #444 and identify which test descriptions the proposed convention should cover. Define the convention and document it where the project keeps testing guidance; done means the intended distinction between regression coverage and failure-property tests is agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100