Types of Testing
White-box testing (also known as clear box testing , glass box testing , transparent box testing , and structural testing ) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing ). White-box testing
In computer programming , unit testing is a method by which individual units of source code , sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures, are tested to determine if they are fit for use. [ 1 ] Intuitively, one can view a unit as the smallest testable part of an application.
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements . System testing falls within the scope of black box testing , and as such, should require no knowledge of the inner design of the code or logic. [ 1 ] As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). System testing
Stress testing (sometimes called torture testing ) is a form of deliberately intense or thorough testing used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. Stress testing
Software performance testing In software engineering , performance testing is in general testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability , reliability and resource usage.
Scenario testing Scenario testing is a software testing activity that uses scenarios : hypothetical stories to help the tester work through a complex problem or test system. The ideal scenario test is a credible, complex, compelling or motivating story the outcome of which is easy to evaluate. [ 1 ] These tests are usually different from test cases in that test cases are single steps whereas scenarios cover a number of steps. [ 2 ] [ 3 ]
Regression testing is any type of software testing that seeks to uncover new software bugs , or regressions , in existing functional and non-functional areas of a system after changes, such as enhancements, patches or configuration changes, have been made to them.
Integration testing Integration testing (sometimes called Integration and Testing, abbreviated "I&T") is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing . Integration testing takes as its input modules that have been unit tested , groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing .
Black-box testing Black box diagram
Functional testing is a quality assurance (QA) process [ 1 ] [ 2 ] and a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (not like in white-box testing ). [ 3 ] Functional Testing usually describes 'what' the system does. Functional testing
Compare with Test automation . Manual testing is the process of manually testing software for defects. Manual testing
Graphical user interface testing In software engineering , graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its written specifications. This is normally done through the use of a variety of test cases . [ edit ] Test Case Generation
GUI Testing Checklist Click here to view the complete list of archived articles