Black box testing - This type of Testing shouldn't be primarily based on any knowledge of internal design or coding. These Tests are based mostly on necessities 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 - probably the most 'micro' scale of testing; to test specific functions or code modules. This is typically accomplished by the programmer and not by testers, because it requires detailed information of the internal program, design and code. Not all the time simply done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.

Incremental integration testing - continuous testing of an application when new functionality is added; requires that various facets of an application's functionality be independent enough to work separately earlier than all elements of the program are completed, or that test drivers be developed as wanted; completed by programmers or by testers.

Integration testing - testing of combined elements of an application to find out in the event that they functioning collectively correctly. The 'parts' will be code modules, particular person applications, shopper and server applications on a network, etc. This type of testing is especially related to shopper/server and distributed systems.

Functional testing - this testing is geared to functional necessities of an application; this type of testing needs to be performed by testers. This doesn't mean that the programmers should not check that their code works before releasing it (which after all applies to any stage of testing.)

System testing - this relies on the overall requirements specifications; covers all the mixed parts of a system.

Finish-to-finish testing - this is similar to system testing; entails testing of an entire application atmosphere in a scenario that imitate real-world use, reminiscent of interacting with a database, using network communications, or interacting with other hardware, applications, or systems.

Sanity testing or smoke testing - typically this is an preliminary testing to determine whether a new software model is performing well sufficient to just accept it for a serious testing effort. For example, if the new software is crashing systems in every 5 minutes, making down the systems to crawl or corrupting databases, the software might not be in a traditional condition to warrant additional testing in its current state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It's tough to determine how a lot re-testing is needed, particularly at the finish of the development cycle. Automated testing instruments are very useful for this type of testing.

Acceptance testing - this may be said as a remaining testing and this was done based on specs of the top-consumer or buyer, or primarily based on use by finish-users/customers over some limited period of time.

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

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

Performance testing - the term often used interchangeably with 'stress' and 'load' testing. Ideally 'efficiency' testing is defined in requirements documentation or QA or Test Plans.

Usability testing - this testing is finished for 'person-good friendliness'. Clearly this is subjective, and will depend upon the focused finish-user or customer. Consumer interviews, surveys, video recording of user periods, and different strategies may be used. Programmers and testers are normally not suited as usability testers.

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

Person acceptance testing - determining if software is satisfactory to a end-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 changes should be made as a result of such testing. This is typically accomplished by end-customers or others, however not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and remaining bugs and problems have to be found before closing release. This is typically carried out by end-customers or others, not by programmers or testers.

If you loved this informative article and you wish to receive details relating to software testing exam generously visit our web site.