Black box testing - This sort of Testing just isn't based mostly on any information of inside design or coding. These Tests are based on requirements and functionality.
White box testing - This is based on data of the inner logic of an application's code. Tests are based mostly on coverage of code statements, branches, paths, conditions.
Unit testing - essentially the most 'micro' scale of testing; to test specific capabilities or code modules. This is typically achieved by the programmer and not by testers, as it requires detailed information of the internal program, design and code. Not all the time easily carried out unless the application has a well-designed architecture with tight code; could require developing test driver modules or test harnesses.
Incremental integration testing - continuous testing of an application when new functionality is added; requires that numerous elements of an application's functionality be independent sufficient to work separately before all elements of the program are accomplished, or that test drivers be developed as wanted; accomplished by programmers or by testers.
Integration testing - testing of combined components of an application to find out in the event that they functioning together correctly. The 'elements' might be code modules, particular person applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing - this testing is geared to functional requirements of an application; this type of testing must be finished by testers. This doesn't suggest that the programmers shouldn't check that their code works earlier than releasing it (which in fact applies to any stage of testing.)
System testing - this is predicated on the overall necessities specifications; covers all of the combined parts of a system.
Finish-to-end testing - this is much like system testing; includes testing of a complete application surroundings in a state of affairs that imitate real-world use, reminiscent of interacting with a database, utilizing network communications, or interacting with other hardware, applications, or systems.
Sanity testing or smoke testing - typically this is an initial testing to find out whether or not a new software version is performing well enough to simply accept it for a serious testing effort. For instance, if the new software is crashing systems in every 5 minutes, making down the systems to crawl or corrupting databases, the software will not be in a normal condition to warrant additional testing in its present state.
Regression testing - this is re-testing after bug fixes or modifications of the software. It's difficult to determine how a lot re-testing is required, especially at the finish of the development cycle. Automated testing tools are very helpful for this type of testing.
Acceptance testing - this may be said as a closing testing and this was performed based mostly on specifications of the top-person or buyer, or based mostly on use by finish-users/prospects over some limited period of time.
Load testing - this is nothing but testing an application below heavy loads, resembling testing a web site underneath a range of loads to find out at what point the system's response time degrades or fails.
Stress testing - the term often used interchangeably with 'load' and 'efficiency' testing. Also used to explain such tests as system functional testing while under unusually heavy loads, heavy repetition of sure actions or inputs, input of large numerical values, large complicated queries to a database system, etc.
Efficiency testing - the term usually used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing is defined in necessities documentation or QA or Test Plans.
Usability testing - this testing is finished for 'person-friendliness'. Clearly this is subjective, and can rely on the focused end-consumer or customer. Person interviews, surveys, video recording of consumer periods, and other methods could be used. Programmers and testers are usually not suited as usability testers.
Compatibility testing - testing how well the software performs in a specific hardware/software/operating system/network/etc. environment.
User acceptance testing - figuring out if software is satisfactory to a end-user or a customer.
Comparability testing - comparing software weaknesses and strengths to other competing products.
Alpha testing - testing an application when development is nearing completion; minor design changes should be made as a result of such testing. This is typically executed by finish-users or others, however not by the programmers or testers.
Beta testing - testing when development and testing are essentially accomplished and closing bugs and problems have to be discovered before closing release. This is typically carried out by end-customers or others, not by programmers or testers.
If you loved this write-up and you would like to receive more information about test plan in software testing
kindly pay a visit to our site.