Automated testing
Open
- Dominant language
- C
- Stars
- 118
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
It would be useful to have some form of automated testing to
1. verify the .md is correct syntax
2. the structure of the .md is consistent, e.g. wrt whitespace between problems
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's .md files to identify the syntax and structural conventions that automated checks would need to enforce. Done means checks detect invalid Markdown syntax and inconsistent whitespace between problems; no specific test files or entry points are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100