Experience Based Test technique?

We have gone through Blackbox testing techniques like equivalence partitioning and boundary value analysis. These approaches are more structured, and there is a clear approach defined to apply these techniques. If multiple testers apply the same technique on a requirement, then they will produce a similar set of test cases.

When applying experience-based test techniques, the test cases are derived from the tester’s skill and intuition. Their past works with similar applications and technologies also play a role in this. These techniques can be helpful in looking out for tests that were not easily identified by other structured ones. Depending on the tester’s approach, it may achieve widely varying degrees of coverage and effectiveness. Coverage can be difficult to assess and may not be measurable with these techniques.

When should we use experience-based technique?

• Requirements and specifications are not available.
• Requirements are inadequate.
• Limited knowledge of the software product.
• Time constraints to follow a structured approach.

For example, if you test an eCommerce application like Amazon, there are some scenarios that a tester would know from his experience that a casual user might not try such as:

• Enter a negative value in the quantity field.
• Order multiple products or quantities, apply a discount code on the cart value, and then return some quantity. E.g. if you bought 3 quantities at 100 each and then applied a 10% discount your final amount is 270. When you return one quantity, you should get 90 refunded and not 100.
• Also, try logging into multiple sessions and see if cart gets updated correctly.
• Add a product in cart and make it out of stock from the backend.
• Add product to cart, enter payment details, and just before clicking place order make it out of stock from the backend.