Black box testing - This form of Testing will not be primarily based on any data of internal design or coding. These Tests are primarily based on necessities and functionality.

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

Unit testing - the most 'micro' scale of testing; to test specific functions or code modules. This is typically carried out by the programmer and not by testers, because it requires detailed information of the internal program, design and code. Not at all times easily achieved unless the application has a well-designed architecture with tight code; may require creating test driver modules or test harnesses.

Incremental integration testing - steady testing of an application when new functionality is added; requires that numerous facets of an application's functionality be unbiased sufficient to work separately earlier than all parts of the program are completed, or that test drivers be developed as needed; completed by programmers or by testers.

Integration testing - testing of mixed parts of an application to determine if they functioning together correctly. The 'components' may be code modules, individual applications, consumer and server applications on a network, etc. This type of testing is very 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 completed by testers. This does not imply 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 general requirements specifications; covers all the mixed components of a system.

Finish-to-end testing - this is just like system testing; includes testing of a complete application surroundings in a scenario that imitate real-world use, such as 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 find out whether a new software version is performing well sufficient to accept it for a major testing effort. For instance, if the new software is crashing systems in each 5 minutes, making down the systems to crawl or corrupting databases, the software will not be in a traditional situation to warrant further testing in its present state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It is troublesome to determine how much re-testing is needed, especially on 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 done based on specs of the top-user or buyer, or primarily based on use by end-customers/prospects over some limited interval of time.

Load testing - this isn'thing however testing an application underneath heavy loads, similar to testing a web site under a range of loads to determine at what point the system's response time degrades or fails.

Stress testing - the time period typically used interchangeably with 'load' and 'performance' testing. Additionally used to describe such tests as system functional testing while beneath unusually heavy loads, heavy repetition of sure actions or inputs, enter of enormous numerical values, massive advanced 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 'user-palliness'. Clearly this is subjective, and will depend on the targeted finish-person or customer. User interviews, surveys, video recording of user classes, and other methods can be used. Programmers and testers are often not suited as usability testers.

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

Consumer acceptance testing - figuring out if software is satisfactory to a finish-consumer 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 on account 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 ultimate bugs and problems have to be discovered before final release. This is typically finished by finish-customers or others, not by programmers or testers.

If you beloved this report and you would like to get more facts concerning softwate testing material kindly take a look at the website.