Error Guessing
This is a classic symbol of experience based testing.
In this technique, the tester can use his/her exposures about the application behavior and functionalities to hunch the error-prone areas. Many defects can be construct using error guessing where most of the developers consistently make mistakes.
In this technique, the tester can use his/her exposures about the application behavior and functionalities to hunch the error-prone areas. Many defects can be construct using error guessing where most of the developers consistently make mistakes.
Few common blunder that developers usually blow to handle::
•
Divide by zero.
• Conduct null values in text fields.
• Accepting the Submit button without any amount.
• Folder upload without attachment.
• Folder upload with less than or more than the limit size.
• Null pointer exception.
• Invalid parameters
• Accepting the Submit button without any amount.
• Folder upload without attachment.
• Folder upload with less than or more than the limit size.
• Null pointer exception.
• Invalid parameters
Following aspects can be used to guess the errors:
•
Lessons learned from history releases
•
Tester’s intuition
•
Historical learning
•
Previous defects
•
Production tickets
•
Review checklist
•
Application User Interface
•
Previous test results
•
Risk reports of the application
•
Variety of data used for testing.
•
General testing rules
•
Knowledge about AUT
The achievement amount of this technique does chiefly depend upon the competence of testers. It is mainly based on intuition and experience.
It should be usually operate once most of the formal testing techniques have been enforced.
0 Comments