example suggestions: demonstrate using a separate file for tests
Open
Nobody has claimed this yet.
example suggestion
good first issue
- Dominant language
- Shell
- Stars
- 46
- Forks
- 19
- Avg merge
- 13h 38m
- Merged PRs (30d)
- 19
Description
Currently we've always put expect tests in the same file as the code, for some cases it's nice to have a separate file for tests, so we should show how to do this.
This example could be useful if you don't have much Roc experience yet.
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
Review the existing examples and the referenced MultipleRocFiles example first, then identify where the current same-file expect tests are demonstrated. Add an example showing tests in a separate file, and confirm the example clearly communicates that arrangement and remains runnable.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100