Let’s see, What is Experience Based Testing. Experience-based techniques are based on the tester’s experience with testing, development, similar applications, the same application in previous releases, and the domain itself. The tester brings all their knowledge to bear when designing the test cases.
Experience Based Testing
Experience-based techniques go together with specification-based and structure-based techniques, and it is used when there is no specification, or if the specification is inadequate or out of date.
Following are the types of Experience Base Testing :
Checklist based Testing
Experience-based testing isn’t an excuse to have poor testing documentation or to jump into testing with no plan. Experienced testers know what needs to be documented to assess coverage and ensure some level of repeatability.
Following four major types of experience-based testing.
1) Error guessing
2) Checklist based Testing
3) Exploratory Testing
4) Attack Testing
Error guessing is commonly used in risk analysis to “guess” where errors are likely to occur and to assign a higher risk to the error-prone areas. Error guessing as a testing technique is employed by the tester to determine the potential errors that might have been introduced during the software development and to devise methods to detect those errors as they manifest into defects and failures.
Error guessing coverage is usually determined based on the types of defects that are being sought. If there is a defect available, that can be used as the guideline. If taxonomy is not employed, the experience of the tester and the time available for testing usually determine the level of coverage.
Checklist-based testing is used by experienced testers who are using checklists to guide their testing. The checklist is basically a high-level list, or a reminder list, of areas to be tested. This may include items to be checked, lists of rules, or particular criteria or data conditions to be verified. Checklists are usually developed over time and draw on the experience of the tester as well as on standards, previous trouble-areas, and known usage scenarios. Coverage is determined by the completion of the checklist.
Remember that exploratory testing is not ad hoc testing. Exploratory testing occurs when the tester plans, designs, and executes tests concurrently and learns about the product while executing the tests. As testing proceeds, the tester adjusts what will be tested next based on what has been discovered. Exploratory tests are planned and usually guided by a test charter that provides a general description of the goal of the test. The process is interactive and creative, ensuring that the tester’s knowledge is directly and immediately applied to the testing effort. Documentation for exploratory testing is usually lightweight if it exists at all.
Software attacks (sometimes called fault attacks) are focused on trying to induce a specific type of failure. When performing attack testing, you should consider all areas of the software and its interaction with its environment as opportunities for failures. Attacks target the user interface, the operating system, interfacing systems, database interfaces, APIs, and any file system interaction. Anytime data is being exchanged, it is potentially vulnerable to a failure and consequently is an excellent target for an attack.
1) Experience-based testing can have huge benefits, as can be seen from several examples. But it is better to use these techniques wisely.
2) Experience-based testing isn’t an excuse to have poor testing documentation or to jump into testing with no plan.
3) This type of testing is most effective in the hands of experienced testers who will bring their knowledge to bear in the most productive ways possible.
a) Experienced testers know what needs to be documented to assess coverage and ensure some level of repeatability.
Products from Amazon.in
Price: Check on Amazon
Price: INR 29,999.00
Price: INR 15,390.00
b) Experienced testers also know what to target to find the biggest bugs quickly and return a high yield during their testing time.
4) These are not techniques for novices-but they are definitely appropriate and productive techniques for the advanced tester.