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 Experience Based Testing Techniques?
The experience based testing technique is utilizing tester’s skill, intuition and experience with similar applications or technologies.
- It is useful when proper specifications are not available to test the applications.
- This technique is used for low risk systems.
- Can yield varying degrees of effectiveness.
Some of the reasons to use experience based testing techniques are:
- Non –availability of requirements and specifications.
- Limited knowledge of software product
- Time restrictions
- Experience based testing finds more defects, that’s the main reason why it is done.
Here are some statistics:
- Discovers approximately 11% more overall defects than scripted testing.
- In case of complex scenarios where many user actions are required, probability to find “complex” bugs jumps to 33% more defects found.
- Experienced testing allows you to think outside the box and come up with use cases that might not be covered in a test case.
Software application or products having higher risks may also be tested through this technique but should be accompanied by the formal & effective testing procedures and documentation.
Benefits of Exploratory testing:
Below are some of the most important benefits of exploratory testing:
- Less effort is required in preparation of exploratory test as it doesn’t require predefined test plans, less preparation is required, meaning you can start testing earlier.
- It fills the gaps left by automated testing. Not everything is automatable, so exploratory testing can be a useful way to test what automation testing can not.
- It detects edge-case defects and unexpected behaviors. Scripted testing tends to focus on the happy path.
- It helps testers, and QA professionals know a given system. Exploratory testing helps newcomers to a team get to know a given application.
The different types of experience based techniques are:
1) Random Testing:
It is a black box testing technique where all of the test inputs are generated randomly (often using a tool) and used for testing. Please click here for more detailed description.
2) Exploratory Testing:
It is a hands-on approach in which testers are involved in minimum planning and maximum test execution.Please click here for more detailed description.
Exploratory software testing is done on the go and relies on the testers imagination and creativity. Exploratory testers design a test, execute it immediately, observe the results, and use results to design the next test.With scripted testing, the application code must exist, in a testable state, before the QA team can develop and execute on test cases.
Please click here for more detailed description.
3) Error Guessing:
It is a Software Testing technique on guessing the error which can prevail in the code.
The main purpose of this technique is to guess possible bugs in the areas where formal testing would not work.
Please click here for more detailed description.
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