What Kinds Of Software Testing Should Be Considered

What Kinds Of Software Testing Should Be Considered

Black box testing - This kind of Testing is not based on any knowledge of internal design or coding. These Tests are primarily based on necessities and functionality.

White box testing - This is predicated on knowledge of the interior logic of an application's code. Tests are based mostly on coverage of code statements, branches, paths, conditions.

Unit testing - the most 'micro' scale of testing; to test particular capabilities or code modules. This is typically executed by the programmer and not by testers, as it requires detailed knowledge of the inner program, design and code. Not always simply finished unless the application has a well-designed architecture with tight code; may require growing 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 parts of the program are accomplished, or that test drivers be developed as wanted; performed by programmers or by testers.

Integration testing - testing of combined parts of an application to determine in the event that they functioning together correctly. The 'parts' can be code modules, individual applications, consumer and server applications on a network, etc. This type of testing is particularly related to shopper/server and distributed systems.

Functional testing - this testing is geared to functional requirements of an application; this type of testing should be finished by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

System testing - this is predicated on the overall requirements specs; covers all of the mixed parts of a system.

End-to-finish testing - this is similar to system testing; includes testing of a whole application environment in a situation 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 initial testing to determine whether a new software version is performing well enough 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 may not be in a normal condition to warrant further testing in its present state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It's difficult to find out how much re-testing is needed, especially on the end of the development cycle. Automated testing instruments are very useful for this type of testing.

Acceptance testing - this may be said as a final testing and this was accomplished primarily based on specs of the end-person or buyer, or 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, akin to testing a web site under a range of loads to find out at what level the system's response time degrades or fails.

Stress testing - the term often used interchangeably with 'load' and 'performance' testing. Additionally used to explain such tests as system functional testing while under unusually heavy loads, heavy repetition of sure actions or inputs, input of enormous numerical values, giant complex queries to a database system, etc.

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

Usability testing - this testing is completed for 'consumer-good friendliness'. Clearly this is subjective, and can rely on the targeted end-consumer or customer. Person interviews, surveys, video recording of user classes, and different techniques may be used. Programmers and testers are normally not suited as usability testers.

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

Consumer acceptance testing - determining if software is satisfactory to a end-consumer or a customer.

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

Alpha testing - testing an application when development is nearing completion; minor design modifications should be made on account of such testing. This is typically done by finish-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 earlier than ultimate release. This is typically done by end-users or others, not by programmers or testers.

If you enjoyed this information and you would certainly like to receive additional details relating to cania-consulting.com kindly go to our web-site.
© Copyright 2013