Testing Foundation
What is Software Testing?
Objective of Testing
Why is testing necessary?
Common Terms used in Testing
Verification Vs Validations
QA Vs QC
Debugging Vs Testing
Seven Testing Principles
SDLC Vs STLC
Fundamentals of Test Process
Software quality Factors
Software Development Models
Waterfall Model
V models
Iterative Model
Test Levels
Component Testing
Integration Testing
System Testing
Acceptance Testing
Strategies for Integration Testing
Big Bang
Stubs and Driver
Top Down Testing
Bottom Up Testing
Test Types
Functional Testing
Non- Functional Testing
Structural Testing
Re-testing & Regression Testing
Static AND Dynamic Techniques
Static Technique
Dynamic Technique
Static Analysis by Tools
White Box Techniques
Statement Coverage Testing
Branch Coverage Testing
Decision Coverage Testing
Path Coverage
Black Box Techniques
Equivalence Partitioning
Boundary Value Analysis
Decision Table testing
State Transition testing
Experience Based TestingTechniques
Random Testing
Exploratory Testing
Error Guessing
Functional Testing
Integration Testing
Unit Testing
System Testing
Smoke testing
Sanity testing
Regression Testing
Usability Testing
Security Testing
User Acceptance Testing
White Box & Black Box Testing
Globalization & Localization Testing
Non Functional Testing
Compatibility testing
Endurance testing
Load testing
Performance testing
Recovery testing
Scalability testing
Stress testing
Volume testing
Test Planning and Estimation
Test Planning
Test Strategies Vs Test Plan
Test Approaches
Risk and Testing
Product Risks
Project Risks
Defect Management
Defect LifeCycle
Severity Vs Priority
What is Error Guessing Testing Technique?
Error Guessing technique is a Software Testing technique on guessing the error which can prevail in the code.
Error guessing is a black box testing technique that relies on the tester’s experience and intuition to identify potential errors or defects in a software system. This technique involves guessing the types of errors or defects that are likely to occur and then designing test cases to detect them.
The main purpose of this technique is to guess possible bugs in the areas where formal testing would not work.
- Experience of the tester is utilised to guess the problematic areas of the application.Â
- This technique necessarily requires skilled and experienced testers.
- It is a type of Black-Box Testing technique and can be viewed as an unstructured approach to Software Testing.
- This technique can be used at any level of testing.
-  It is the process of making an educated guess as to other types of areas to be tested.Â
- main purpose is to concentrate the testing action on regions that have not been taken care of by the other more formal methods.
For example:
Suppose you are testing a login page for a application and you are asked to identify any possible errors that may occur during the login process. By error guessing technique, you might consider the following scenarios:
- Entering an invalid username and password combination
- Entering a valid username but an incorrect password
- Attempting to login with a username or password that exceeds the maximum character limit
- Attempting to login with a username or password that does not meet the required complexity criteria
- Entering a valid username and password but with the caps lock key on
- Attempting to login without entering any credentials
- Attempting to login with special characters in the username or password field
By considering these scenarios, you can identify potential errors that might occur during the login process and design test cases to verify that the system behaves correctly under these conditions. The goal is to uncover potential issues that may not have been identified by other testing methods, ultimately improving the quality of the software.
Some common areas of error guessing:
- Divide by zero
- Null pointer exception
- Entering blank spaces in the text fields
- Pressing the submit button without entering values.
- Uploading files exceeding maximum limits.
- Invalid parameters
- Refresh buttons
Benefits/Advantages of Error Guessing technique:
- Effective when used in combination with other formal testing techniques.
- Reveals those defects which would otherwise not be possible to find out, through formal testing.Â
- Saves a lot of time and effort.
- Helps in errorguessing of complex and problematic areas of the application.
Drawbacks of ErrorGuessing technique:
- Dependent on testers experience and skills
- Does not guarantee that the software has reached the expected quality.
- Does not provide full coverage of the application
In Conclusion , Error guessing can be a useful addition to a comprehensive testing strategy, but it should not be relied upon as the sole method of testing a system. By combining error guessing with other testing techniques, such as functional testing and regression testing, testers can more effectively identify and address errors or defects in a software system.
Recommended Articles:
Testing Foundation
What is Software Testing?
Objective of Testing
Why is testing necessary?
Common Terms used in Testing
Verification Vs Validations
QA Vs QC
Debugging Vs Testing
Seven Testing Principles
SDLC Vs STLC
Fundamentals of Test Process
Software quality Factors
Software Development Models
Waterfall Model
V models
Iterative Model
Test Levels
Component Testing
Integration Testing
System Testing
Acceptance Testing
Strategies for Integration Testing
Big Bang
Stubs and Driver
Top Down Testing
Bottom Up Testing
Test Types
Functional Testing
Non- Functional Testing
Structural Testing
Re-testing & Regression Testing
Static AND Dynamic Techniques
Static Technique
Dynamic Technique
Static Analysis by Tools
White Box Techniques
Statement Coverage Testing
Branch Coverage Testing
Decision Coverage Testing
Path Coverage
Black Box Techniques
Equivalence Partitioning
Boundary Value Analysis
Decision Table testing
State Transition testing
Experience Based TestingTechniques
Random Testing
Exploratory Testing
Error Guessing
Functional Testing
Integration Testing
Unit Testing
System Testing
Smoke testing
Sanity testing
Regression Testing
Usability Testing
Security Testing
User Acceptance Testing
White Box & Black Box Testing
Globalization & Localization Testing
Non Functional Testing
Compatibility testing
Endurance testing
Load testing
Performance testing
Recovery testing
Scalability testing
Stress testing
Volume testing
Test Planning and Estimation
Test Planning
Test Strategies Vs Test Plan
Test Approaches
Risk and Testing
Product Risks
Project Risks
Defect Management
Defect LifeCycle
Severity Vs Priority