Gia Long

Switch to desktop

What Kinds Of Software Testing Should Be Considered

What Kinds Of Software Testing Should Be Considered

Black box testing - This form of Testing shouldn't be based mostly on any knowledge of internal design or coding. These Tests are based on requirements and functionality.

White box testing - This is based on knowledge of the interior logic of an application's code. Tests are primarily based 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 never by testers, as it requires detailed knowledge of the inner program, design and code. Not always easily carried out 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 numerous facets of an application's functionality be impartial sufficient to work separately before all parts of the program are completed, or that test drivers be developed as needed; accomplished by programmers or by testers.

Integration testing - testing of mixed parts of an application to find out in the event that they functioning collectively correctly. The 'parts' could be code modules, particular person applications, client and server applications on a network, etc. This type of testing is very relevant to client/server and distributed systems.

Functional testing - this testing is geared to functional requirements of an application; this type of testing ought to be achieved by testers. This does not imply that the programmers shouldn't check that their code works before releasing it (which in fact applies to any stage of testing.)

System testing - this is based on the overall requirements specifications; covers all the combined elements of a system.

End-to-finish testing - this is similar to system testing; entails testing of a whole application environment in a state of affairs that imitate real-world use, corresponding to interacting with a database, using network communications, or interacting with different hardware, applications, or systems.

Sanity testing or smoke testing - typically this is an preliminary testing to find out whether a new software model is performing well sufficient to accept it for a major 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 is probably not in a traditional 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 tough to determine how much re-testing is required, especially at the end of the development cycle. Automated testing tools are very useful for this type of testing.

Acceptance testing - this can be said as a final testing and this was performed based on specs of the tip-person or customer, or based mostly on use by finish-users/clients over some limited interval of time.

Load testing - this just isn'thing however testing an application beneath heavy loads, reminiscent of 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 explain such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, massive complicated 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 finished for 'person-palliness'. Clearly this is subjective, and can depend upon the targeted end-consumer or customer. Consumer interviews, surveys, video recording of user classes, and different methods may be used. Programmers and testers are usually not suited as usability testers.

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

User acceptance testing - figuring out if software is satisfactory to a finish-person 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 may still be made because of such testing. This is typically done by end-customers or others, but not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and last bugs and problems have to be discovered earlier than final release. This is typically finished by end-customers or others, not by programmers or testers.

If you loved this article and you simply would like to obtain more info relating to software testing value nicely visit the page.
Email: This email address is being protected from spambots. You need JavaScript enabled to view it.