Skip to main content

Exact Difference between Adhoc and Exploratory Testing

Difference between Adhoc and Exploratory Testing

           Adhoc Testing
            Exploratory Testing
1. Adhoc Testing means learn the application than test it.
1. Exploratory Testing means test the application while learning.
2. In Exploratory Testing QA is always asked to test an application without any specific set of documents.
2. In Adhoc Testing QA is always asked to test an application with detailed set of documents.
3. In this Testing we always gather information regarding the software/application from complete possible sources and document and then test the application/software.
3. In this Testing we gather the information, and also document and test the application simultaneously.
4. In Adhoc Testing tester should have good knowledge about the application in order to test the software.
4. In Exploratory Testing tester should increases their knowledge by exploring the application/software.
5. In this testing testers have significant testing of the software before test it.
5. In this testing testers may be learning the software before testing it.
6. It is not considered as a type of any.
6. It is considered as a type of Adhoc Testing
7. It is not an approach to testing.
7. It is an approach, not a technique.


Labels:

Comments

  1. AnonymousJuly 3, 2015 at 11:14 AM

    Interchange the 2nd point in Adhoc &Exploratory testing difference table

    ReplyDelete
  2. AnonymousDecember 11, 2015 at 10:16 PM

    Thats what I was gona write

    ReplyDelete

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...
Post a Comment
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more