Features testing.
Open
Nobody has claimed this yet.
question
- Dominant language
- Kotlin
- Stars
- 1.3k
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys. Do you have any examples, best practices how you tests yours features?
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
No files, tests, or entry points are identified. First clarify which feature-testing examples or best practices are wanted, then document the agreed guidance and verify that it addresses the requested examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, testing
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100