While I was surfing the internet, I found the terms “Monkey Testing” where it has nothing to do with Penetration Testing. Monkey Testing can be categorized as a software testing technique.
Why Monkey Testing?
As we all know, Monkey is an animal that like to randomly touch anything on the keyboard from their actual task understanding. Due to that, System Tester can done random test-case without following the actual case study that provided by the System Developer.
The Monkey Testing can also dedicated to case study such as listed below:
- GUI Testing
- Unit Testing
GUI(Graphic User Interface) testing is an testing which the tester will test their functionality of the system whether its working properly according to the case study.
So basically, the tester will try to check on the interface itself such as Button Functionality, Link Functionality, and Design Functionality. GUI Testing will not provide any access to the program source code.
Unit Testing is testing where the tester will check the component of the software/application that been used. Normally, Unit Testing is been run to check whether the component is been configured correctly.
Type of Monkey Testing
There is a total of 3 type of Monkey Testing that been used by System Tester such as:
- Dumb Testing
- Smart Testing
- Brilliant Testing
Dumb Testing is a test where the System Tester will not have any knowledge about the system or application. It is similar to BlackBox Testing( Penetration Testing term).
Smart Testing is a test where the System Tester has an exact knowledge on what is been configure and functionality that has been implemented on the system itself.
Brilliant Testing is a test where the System Tester will need to test the system according to the user’s behaviour and driven to find bugs that might be occurred.
Advantages vs Disadvantages
The advantages of Monkey Testing are been listed below:
- New bug can be found even non-skilled tester resources can be hired for the job. It also cannot be found within the case study that been provided by the System Developer.
- Since this activity will be Ad-hoc, Stress Testing can be included on the case study and also the setup for Monkey Testing would be an easy which it is good for the application itself
The reader can also see the disadvantages of the Monkey Testing as listed as follows:
- Although, new bug can be found on the system but the bug cannot be reproduce. Besides, it would be time consuming in terms of analyzing the bug. This is also may cause a difficult to find a lot of loopholes that can impact the system.
- It also don’t produce any guarantee whether the case study or bug found during the Monkey Testing can be considered as accuracy.
- It can also be costly where the organization will need to hired a very good technical expertise of the domain.