Types of testing
Types of testing
Testing shows the presence of defects: The objective is to identify as many bugs as
possible.
Exhaustive testing is not possible: Careful planning and assessment of the testing
process will save one from testing every single line of code.
Early testing saves time and money: Fixing issues early is an easier and cheaper
option than doing the same toward the end of the product’s life cycle.
Defects cluster together: Testing should be focused on those areas of the software
that usually have the most issues.
Beware of the pesticide paradox: It is important to update testing techniques to
help prevent the pesticide paradox.
Testing is context-dependent: The testing that is carried out depends on the
context of the software or systems.
The absence of errors is a fallacy: If a system does not fulfill the specified
requirements, then no matter how many errors are found and fixed, it will still be
unusable.
Applying these principles effectively helps to improve the quality of the overall
testing strategy and achieve optimum efficiency.
Check out our blog on Selenium tutorial to learn how to automate testing using
Selenium!
Cost-effective development: As discussed already, early testing saves both time and
cost.
Product improvement: Diagnosing and amending the errors after proper testing can be
time-consuming but is a way for product improvement.
Quality: Software testing helps to keep in check the following in a system or
software:Functionality
Usability
Efficiency
Reliability
Maintainability
Portability
Client confidence: For forging long-term relationships with clients, making
software testing a clear priority is incredibly important.
White-box Testing
Black-box Testing
Grey-box Testing
White-box Testing
White-box testing is also known as structural testing, glass-box testing,
transparent-box testing, or clear-box testing. This kind of testing is executed at
the unit level and is based on the internal code structure. The test cases are
designed based on the internal perspective of the system and programming skills
such as code statements, conditions, branches, paths, etc.
Grey-box Testing
Gray box testing (a.k.a grey box testing) is a method you can use to debug software
and evaluate vulnerabilities. In this method, the tester has limited knowledge of
the workings of the component being tested.
Grey-box testing, as you may have already guessed, is the combination of both
white-box and black-box testing. The testers will have access to design documents
and internal coding for the purpose of designing test cases. The testing process
here is executed at a functionality level.