Ad-hoc Testing
- Ad hoc testing is a commonly used term for software testing performed without planning and documentation.
- The tests are intended to be run only once, unless a defect is discovered.
- Adhoc testing is the least formal test method.
- The strength of ad hoc testing is that important defects can be found quickly.
- A creative and informal way of testing the software
- Conducted without any understanding of the software before testing it
- Not conducted based on formal test plans or test cases
- Performed by Testers
- Performed on a Stable application or product.
- Behavior of the application when the same functionality is executed multiple times.
- Behavior of the application when the previous and next screen navigation is performed more than once.
Approach that is
most useful when there are:
- Inadequate specifications.
- Severe time pressure.
- This is performed to verify the:
- Stability of the application
- This type of testing is done without any formal Test Plan or Test Case creation.
- Testing the application randomly is called ad-hoc testing.
- The way in which end user use the application is totally different the way we do testing, as a test engineers we don’t want any user to find any defects, so we test application randomly.
When to do the Ad-hoc testing
- Don’t do ad-hoc testing soon after smoke testing.
- After the formal testing if we have time and we have some creative idea than we can go for ad-hoc testing.
Exploratory
Testing
- The plainest definition of exploratory testing is test design and test execution at the same time.
- Exploratory tests are not defined in advance and carried out precisely according to plan
- Understand the application write test cases and do testing. Whenever there will be no requirements we go for exploratory Testing.
- It means without requirements we have to test the application.
You may also like:
Complete Testing Material
Testing basic interview questions
No comments:
Post a Comment