luckyframework / luckyframework/website
Document using the backdoor
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 39
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/luckyframework/lucky/issues/1165#issuecomment-683837559
We currently mention to look at the mixin to see how it works, but have a little more docs on testing browser actions with users and using this backdoor stuff would be great.
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 with the linked issue comment and find the current documentation that tells readers to look at the mixin. Read the existing guidance on testing browser actions with users, then expand the documentation to explain the backdoor approach and how it is used. Done means the relevant testing and backdoor workflow is documented clearly in the website.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100