Experience Based Testing

When applying experience-based test techniques, the test cases are derived from the tester’s skill and intuition, and their experience with similar applications and technologies. These techniques can be helpful in identifying tests that were not easily identified by other more systematic techniques. Depending on the tester’s approach and experience, these techniques may achieve widely varying degrees of coverage and effectiveness. Coverage can be difficult to assess and may not be measurable with these techniques

Generally, experience-based testing is considered to be a secondary approach in order to test an application as we identify a formal test approach to be more systematic and measurable. Formal techniques help us to derive required test cases and documented whereas, whereas informal(Experience-based) don't always need the creation of test cases and documenting the details.

At the same time, there are few cases where informal are used as the primary approach to the test. For example, 

• Poor Specification - When requirements are documented at a high level, poorly documented, or don't exist at all, then experience-based testing is the only option to test the built system.
• Time Pressure - In this scenario, the team is running short on time to do a lot of testing. Here, the team can't write detailed test cases and execute and log the results formally. Thus, the team can use experience-based testing to do better testing in a limited time.
• The team is Domain Expert but has no formal training on Testing - There could also be a possibility that the team is domain expert in the type of product they are testing but they are never trained formally on test techniques or test case creation. 

Watch the detailed video here to understand better.

Comment below for any queries