Black box testing - This sort of Testing isn't based on any knowledge of inside design or coding. These Tests are based mostly on necessities and functionality.

White box testing - This relies on information of the interior logic of an application's code. Tests are primarily based on coverage of code statements, branches, paths, conditions.

Unit testing - essentially the most 'micro' scale of testing; to test particular functions or code modules. This is typically carried out by the programmer and never by testers, as it requires detailed data of the interior program, design and code. Not at all times easily completed 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 various aspects of an application's functionality be independent sufficient to work separately earlier than all components of the program are accomplished, or that test drivers be developed as needed; finished by programmers or by testers.

Integration testing - testing of combined components of an application to find out if they functioning collectively correctly. The 'components' could be code modules, individual 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 done by testers. This doesn't mean that the programmers shouldn't check that their code works earlier than releasing it (which after all applies to any stage of testing.)

System testing - this is predicated on the overall necessities specifications; covers all of the mixed elements of a system.

Finish-to-finish testing - this is much like system testing; includes testing of a whole application setting in a situation that imitate real-world use, corresponding to interacting with a database, using network communications, or interacting with different hardware, applications, or systems.

Sanity testing or smoke testing - typically this is an initial testing to find out whether or not a new software model is performing well sufficient to 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 is probably not in a traditional situation to warrant additional testing in its current state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It is difficult to determine how much re-testing is required, particularly at the finish of the development cycle. Automated testing instruments are very helpful for this type of testing.

Acceptance testing - this can be said as a final testing and this was finished based mostly on specs of the tip-consumer or buyer, or primarily based on use by end-users/clients over some limited period of time.

Load testing - this is nothing but testing an application under heavy loads, corresponding to testing a web site beneath a range of loads to find out at what level the system's response time degrades or fails.

Stress testing - the term usually used interchangeably with 'load' and 'performance' testing. Additionally used to describe such tests as system functional testing while below unusually heavy loads, heavy repetition of sure actions or inputs, enter of huge numerical values, giant complex queries to a database system, etc.

Efficiency testing - the term often 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 done for 'person-friendliness'. Clearly this is subjective, and will rely upon the focused finish-person or customer. User interviews, surveys, video recording of user sessions, and other strategies might be used. Programmers and testers are usually not suited as usability testers.

Compatibility testing - testing how well the software performs in a selected hardware/software/operating system/network/etc. environment.

Consumer acceptance testing - figuring out if software is satisfactory to a finish-person or a customer.

Comparability testing - evaluating software weaknesses and strengths to different competing products.

Alpha testing - testing an application when development is nearing completion; minor design adjustments may still be made as a result of such testing. This is typically carried out by end-users or others, but not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and last bugs and problems have to be found earlier than last release. This is typically performed by end-users or others, not by programmers or testers.

Should you loved this short article and you wish to receive much more information relating to managing test reviews kindly visit the page.