Adhoc Testing

What is Adhoc Testing?

This is an unplanned and informal testing type. Main motive of this testing is how to break the functionality of system. No one create any test cases and just started the testing on their individual testing.  Test engineer test the application software or project without any test cases randomly..

Adhoc testing type does not follow any type of structure or any documentation / planning before starting the testing. Here Test engineer should be experienced for that software. Test engineer will test the software randomly and find out the bugs on the base of Error Guessing technique. So this is confirmed that this testing doesn’t require any type of standard process which is required to follow.

When Adhoc Testing should execute?

Adhoc testing should execute only then when there is time limitation for do the formal testing properly. But Adhoc testing can effective only then when the test engineer is fully aware about the system and its functionality otherwise it will not be useful.

Following are the Types of Adhoc Testing:

Buddy Testing: Here two buddies will be start testing with their mutual understanding. One can from development team and another can from Test team. This type help tester to find out the bug very fast and same developer will fixed at a time.

Pair Testing: Here two test engineers can work on same module together so that they can share their ideas, knowledge and work experience.

Monkey Testing: Perform randomly testing of application and product without test cases and main aim will be in mind to break system.

Adhoc Testing Best Practices:

Intelligent Business knowledge: Testing Engineers should intelligent and have good knowledge about related business and software application.

Testing Key Modules: Key modules are those which are most required to test or which are integrated to all required and necessary modules.

Defect Recording: First find out all possible modules and then reporting those to developer in effective and simple way so that anyone can easily understand the bug and  can be decided that bug need to fix or not.

End to End Testing	Negative Vs Positive Testing	Dynamic and Static Testing
Agile Testing	Compatibility Testing	Adhoc Testing
Regression Testing	Non Functional Testing	Test Case
Test Scenario	Software Testing Rules	SQL For Software Testing
Test Case Design and Example	Test Base	Traceability Matrix
Boundary Value analysis	Decision Table in Software Testing	State Transition Definition
Use Case Testing	Testing Review	Techniques of Test Estimation
Test Plan Structure	Definition of Bug	Bug Life Cycle
Automation Testing Tools	Test Web Based Application	Software Testing Types
Software Testing Techniques	Techniques in Software Testing	Test Data
Software Testing Life Cycle	Black Box Testing	Difference between Black Box testing and White Box Testing
Smoke and Sanity Testing	Testing Methodology	Extreme Programming
White Box Testing	System Software Testing	Performance Testing
Usability Testing	User Acceptance Testing	Regression Testing
MANUAL SOFTWARE TESTING	Automation software Testing	Functional Testing

Definition, What is Adhoc Testing, best practices of adhoc testing, types of adhoc testing, Error Guessing technique, requirement of adhoc testing, real world scenarios for adhoc testing

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS