In this
article, we will learn what is Adhoc or Random or more popularly known as Monkey
Testing. why and when we need to use it with some real-time examples.
What is Adhoc, Random or Monkey Testing?
It is
the software testing technique where the user tests the application by
providing the random data or input into the application and observe the
application behavior for any failure.
In this test usually, the tester is considered as Monkey as he is performing any random task without understanding the applications.
Why we do Monkey Testing?
1) End-users use the application randomly and he may see a defect,
but professional TE uses the application systematically so he may not find the
same defect. To avoid this scenario, TE should go and then test the application
randomly (i.e, behave like and end-user and test).
2) The development team looks at the requirements and build the
product. Testing Team also look at the requirements and do the testing. By this
method, the Testing Team may not catch many bugs. They think everything works
fine. To avoid this, we do random testing behaving like end-users.
3) Monkey is testing where we don’t follow the requirements (we
just randomly check the application).
Since
we don’t follow requirements, we don’t write test cases.
For example, Requirement says to test like below ( 1 -> 2
-> 3 -> 4 )
But, we randomly go directly to 4 (this is called Monkey
testing)
Examples of Monkey testing for Gmail:
1) Log in to Gmail using a valid username and password. Logout from
Gmail. Click on the Back button. It should not go back to the Inbox page. If it
does, then it is a javascript error and it is a bug. It should go back to the
Login page and say the session expired.
2) Log in to the Gmail homepage using a valid username and password. Once we are on the Inbox page, copy the URL of the inbox which is in the address bar of the homepage and pastes it in Notepad file. Logout from Gmail. Now, open a browser page and paste the URL of the inbox in the address bar. It should not go to the inbox, instead, it must go to the welcome page of Gmail.
3) Login into Gmail. Go to Settings and Change Password. Set the
old password only as of the new password and see what happens.
Important Point to Note:-
·
Monkey testing is negative testing because we are testing
against requirements (out of requirements).
·
Here, the objective is to somehow break the product.
When to do Monkey Testing?
·
Whenever we are free, we do Ad-hoc testing. i.e, developers
develop the application and give it to the testing team. The testing team is
given 15days for doing FT. In that, he spends 12 days doing FT and another
3days he does Ad-hoc testing. We must always do Ad-hoc testing in the last
because of we 1st concentrate on customer satisfaction.
·
After testing as per requirements, then we start with ad-hoc
testing.
·
When a good scenario comes, we can stop FT, IT, ST and try that
scenario for Ad-hoc testing. But we should not spend more time doing Ad-hoc
testing and immediately resume with formal testing.
·
If there are more such scenarios, then we record it and do it at
the last when we have time.
