What Kinds Of Software Testing Ought To Be Considered

What Kinds Of Software Testing Ought To Be Considered

Black box testing - This kind of Testing shouldn't be primarily based on any knowledge of inner design or coding. These Tests are based mostly 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 particular features or code modules. This is typically performed by the programmer and never by testers, as it requires detailed knowledge of the interior program, design and code. Not always simply accomplished unless the application has a well-designed architecture with tight code; could require growing test driver modules or test harnesses.

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

Integration testing - testing of mixed parts of an application to determine in the event that they functioning together correctly. The 'parts' will be code modules, individual applications, shopper 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 necessities of an application; this type of testing should be done by testers. This doesn't suggest 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 relies on the general necessities specs; covers all the mixed parts of a system.

End-to-end testing - this is much like system testing; includes testing of a complete application surroundings in a situation that imitate real-world use, reminiscent of interacting with a database, utilizing 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 major 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 might not be in a normal 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 difficult to find out how much re-testing is needed, especially at the end of the development cycle. Automated testing tools are very helpful for this type of testing.

Acceptance testing - this will be said as a final testing and this was completed based mostly on specifications of the end-person or customer, or primarily based on use by finish-users/clients over some limited period of time.

Load testing - this is just nothing however testing an application under heavy loads, such as 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 time period usually used interchangeably with 'load' and 'efficiency' testing. Additionally used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, giant complex queries to a database system, etc.

Performance testing - the term typically 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 completed for 'consumer-good friendliness'. Clearly this is subjective, and will depend on the targeted end-person or customer. Person interviews, surveys, video recording of consumer sessions, and other techniques can be used. Programmers and testers are often not suited as usability testers.

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

User acceptance testing - determining if software is satisfactory to a end-user or a customer.

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

Alpha testing - testing an application when development is nearing completion; minor design changes may still be made because of such testing. This is typically completed by end-users or others, however not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and final bugs and problems must be discovered before remaining release. This is typically accomplished by end-customers or others, not by programmers or testers.

Here's more information regarding cania test management take a look at the web site.
   
© Copyright 2013