What Sorts Of Software Testing Ought To Be Considered
White box testing - This is predicated on knowledge of the internal 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 specific features or code modules. This is typically finished by the programmer and not by testers, as it requires detailed data of the inner program, design and code. Not at all times simply 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 various aspects of an application's functionality be impartial enough to work separately earlier than all parts of the program are accomplished, or that test drivers be developed as needed; carried out by programmers or by testers.
Integration testing - testing of combined parts of an application to determine in the event that they functioning collectively correctly. The 'elements' will be code modules, individual applications, consumer and server applications on a network, etc. This type of testing is particularly relevant to consumer/server and distributed systems.
Functional testing - this testing is geared to functional requirements of an application; this type of testing needs to be done by testers. This does not imply 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 based on the overall necessities specs; covers all the mixed elements of a system.
Finish-to-finish testing - this is just like system testing; entails testing of a complete application environment in a scenario that imitate real-world use, resembling 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 find out whether a new software version is performing well sufficient to simply 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 will not be in a standard condition to warrant further testing in its present state.
Regression testing - this is re-testing after bug fixes or modifications of the software. It is tough to find out how much re-testing is required, especially at the end of the development cycle. Automated testing instruments are very helpful for this type of testing.
Acceptance testing - this might be said as a final testing and this was executed primarily based on specifications of the end-consumer or buyer, or based mostly on use by finish-users/clients over some limited period of time.
Load testing - this isn'thing however testing an application beneath heavy loads, resembling testing a web site below a range of loads to find out 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 underneath unusually heavy loads, heavy repetition of certain actions or inputs, enter of enormous numerical values, massive advanced queries to a database system, etc.
Performance testing - the time period 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. Person interviews, surveys, video recording of person classes, and different methods could be used. Programmers and testers are normally not suited as usability testers.
Compatibility testing - testing how well the software performs in a selected hardware/software/operating system/network/etc. environment.
Person acceptance testing - determining if software is satisfactory to a finish-person or a customer.
Comparison testing - comparing software weaknesses and strengths to other competing products.
Alpha testing - testing an application when development is nearing completion; minor design adjustments should still be made because of such testing. This is typically executed by end-users or others, however not by the programmers or testers.
Beta testing - testing when development and testing are essentially accomplished and final bugs and problems must be found earlier than final release. This is typically achieved by end-users or others, not by programmers or testers.
If you want to read more info in regards to test strategy documentation have a look at the website.