TeamAmaze / TeamAmaze/AmazeFileManager
Run monkey tests
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Monkey tests should simulate 1s of user interaction in 1ms of real time, and should run for a specified amount of time. When some crash occurs the test should fail, and a report be generated with the interactions.
Here are two basic runners: App Crawler, Exerciser Monkey.
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
Start by reviewing the repository's Android testing setup and the issue's App Crawler and Exerciser Monkey references. Define how a specified interaction duration, crash failure, and interaction report should be integrated before identifying the relevant test entry points; done means the monkey test runs for the requested time, fails on crashes, and produces a report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100