Ocramius / Ocramius/ocramius.github.com
Blogpost about using static introspection to assess end-to-end test quality / completeness
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 39
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
See this Twitter conversation for reference
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 linked Twitter conversation for the intended topic and context. The issue does not name a source file, test, or entry point, so first identify where blog posts for this repository belong and what scope the post should cover. Done means a published blog post addressing static introspection and end-to-end test quality or completeness.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100