What is the difference between Monkey testing an Ad-hoc
testing (If ur answer is same, then why we need two names)
Answers were Sorted based on User's Feedback
Answer / vikas
Monkey is random testing, u dont know abt the application u
r learnin it.
Ad-hoc is informal testing where u know abt the application
well in hand. You are doing random testing before you
actually begin with the intensive testing.
Definition(s):
Ad-hoc testing : A testing phase where the tester tries to
'break' the system by randomly trying the system's
functionality. Can include negative testing as well.
Monkey Testing : Testing a system or an Application on the
fly, i.e just few tests here and there to ensure the system
or an application does not crash out.
| Is This Answer Correct ? | 53 Yes | 9 No |
Answer / bhanukiran
In general, the exhaustive testing is impossible from
testing principles.Due to this reason,the testing team is
concentrating on Optimal testing.
Some times, the testing team is not able to conduct optimal
testing also,due to some risks.In this situation,the testing
team is conducting Ad-hoc testing or Informal testing.
There are five styles of Ad-hoc testing
1.Monkey testing
2.Buddy testing
3.Exploratory testing
4.Pair testing
5.Debugging.
MONKEY TESTING:
Due to lack of time for testing,the testing
team is concentrating on main activities of that software build.
| Is This Answer Correct ? | 7 Yes | 7 No |
Answer / charulatha
Adhoc Testing :
This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the scope and duration of the various other testing and it also helps testers in learning the application prior starting with any other testing.
Monkey Testing :
If the keyboard is given to monkey , what it ll do ? the same is called monkey testing . randomly testing .
| Is This Answer Correct ? | 3 Yes | 4 No |
Answer / ganesh thik
Adhoc testing-
Adhoc testing is informal testing type.No documentation,test plan is used.Aim to break the system.
Monkey Testing-
Monkey testing is type of adhoc testing.In that randomly test the aapplication
| Is This Answer Correct ? | 2 Yes | 4 No |
Answer / ravi148
ravi148 +91-9951123501
in really secnario., we dont use monkey testing termnology
term.
Adhoc-testing means testing the application with out FTP,
here testers have significant knowledge about the
application.it is useful when time is cunched for release.
monkey testing is nothing but adhoc tsting
| Is This Answer Correct ? | 2 Yes | 6 No |
Answer / praveen samala
Adhoc testing is something which is perfomed when there are
not required documents available and tester past experinece
and the expertise is required for such testing.
Monkey testing is testing the major functionality of the
application when we do not have enough time to test.
| Is This Answer Correct ? | 7 Yes | 17 No |
What is the Test Case?What is the Testing?
10 Answers iSoft, Patni, Verisoft,
Requirement is given : 1) The Login screen should require with 2 fields "Login" & "Password" 2) After successful login Success Message will display. 3) For Invalid login Error Message will display. 4) "Login" & "Password" both fields are case insensitive. 5) The Application should be Dialog application. What are the test cases for above requirements?
When testing a grade calculation system, a tester determines that all scores from 90 to 100 will yield a grade of A, but scores below 90 will not. This analysis is known as: A. Equivalence partitioning B. Boundary value analysis C. Decision table D. Hybrid analysis
what is entry and exit creteria for testing ?
how to select tese cases for automation.give me an example plz.
Which reasons do you use to justify training for the testing team as part of its career development?
What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)
Where you maintains the Repositories
Unit Testing can be done by using Nunit?
What exactly we have to say when interviewer asked "Tell me about your self"?
this question i got from iflex anybody pls give some useful information. is it possible to get severity1bugs in thirds round testing before release after two rounds of system testing completed?
user A done some changes for a portion of test case doc. And user B also done some changes to same portion. If user-A checks in his file first then user-B. Then what is the state of that file?