Page 145 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

2. Semi-Smart Monkey Testing: The next stage of the dumb monkey testing technique is the semi-
smart monkey testing technique. This testing technique is performed by individuals who have
basic knowledge in testing. Semi-smart testing technique is successful when it is performed in
small groups. The services provided by the semi-smart monkey testing technique are as follows:
(a) It is the initial level of planning and acceptance criteria.
(b) It estimates the required staff and time for testing process.

(c) It interprets the requirements prior to running the test.
(d) It makes a note of the semi-technical bug reports and also logs the recording process.
(e) It is also known as the initial level of regression testing.
3. Smart Monkey Testing: Smart monkey testing is the third type of monkey testing. It is commonly
used by testers because of its efficiency. Using the smart monkey testing technique, it is possible
to confirm vast testing projects, make use of different testing tools, and also use the initial testing
theory. This testing technique is restricted to the testing environment. The smart monkey testing
technique is considered to be valuable for stress and load testing as it helps to detect a significant
number of bugs. However, the only area of concern is that it is very expensive to develop this
testing technique. The following services are provided by the smart monkey testing technique:
(a) It helps to track systems usage.

(b) It scrutinizes the requirements prior to running the test.
(c) It creates circumstances for the test.
(d) It helps to track the logs of systems usage.
(e) It also locates memory or resource bugs.
(f) Monkey testing is a valuable testing technique, but not the only testing technique.
9.3 Bug Bashes and Beta Testing

In the earlier sections, we studied the various tools that can be used for testing particular software. We
also learnt about the different testing techniques. In this section we will discuss the other testing
methods.
Bug bash is a tool which is used as a part of the test management program. In this method, all the
developers, testers, program managers, usability researchers, designers and several others are involved
in analyzing the product for bugs. In the bug bash activity, a particular area is selected for testing. The
area to be selected can be free from any bugs or it can be the one causing problems during the
application. The bug bash can determine the bugs which otherwise could not be determined by normal
testing methods. There are many criteria for selecting the area to undergo the bug bash activity.
9.3.1 Test Sharing
Many testers are involved in testing software. All testers will have their own methods and criteria to
locate bugs. The testers have an option of swapping their test responsibilities. This allows both the
testers to analyze the software properly and also complete the testing task. It is also possible that a tester
is unaware of particular software, so by swapping the testing task they can learn the software and also
come up with new tests to detect bugs. The testers can also ask the experienced testers for help. Another
way to get help is by scheduling the bug bash. Given below are a few tips to organize a good bug bash
activity:
1. Involving the Entire Team in the Bug Bash Activity: It is a known fact that the testers would test
the application several times to locate bugs. But if a set of other people, such as designers,
business analysts, testers, developers, release managers, user experience designers, sustained
engineering teams, and even high level managers are involved in the bug bash activity, then it
would be easier to locate bugs if any. Bugs found during the bug bash activity can be a feedback
in itself. This feedback helps in making proper decisions in releasing the software into the
market.

138 LOVELY PROFESSIONAL UNIVERSITY