- This topic has 2 replies, 3 voices, and was last updated 1 year, 10 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Home › Forums › Software Testing Discussions › Monkey Testing in Test Plan
Recently I came across this interesting tool called gremlinsjs shared by DanBilling in one of the testing community slack. As I read it looks like very much useful for monkey testing.
Which made me think if it is a common practice to include such tests in your test plan? if so what kind of products are you testing with?
from this link, https://css-tricks.com/intro-monkey-testing-gremlins-js/ gremlinsjs looks interesting that it can be added to our smoke test suite.
10 years ago monkey testing was in our contract: our application must have been passed certain number of long monkey runs
Later I used my implementation of a “monkey” tool, and was explicitly asked for that, but it was not on test plan.
Monkey testing will help to get some level of stress test on your app. It generate the random UI actions that help to identify the some hidden bugs.
When you run such test on browser keep eye one browser console where you might see New errors or waning!
Chrome extension :
https://chrome.google.com/webstore/detail/gremlinjs-testing-extensi/eamcocddjlpbghfbicddnloonlclafic
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.