Bruce Jay Mack - iCIS Knowledge base and Collaboration WikiWiki
Welcome
Guest
, you are in:
<root>
iCIS
PTC
•
Login
Test Wiki
Navigation
¶
Main Page
Random Page
Create a new Page
All Pages
Categories
Navigation Paths
Administration
File Management
Create Account
Search the wiki
»
Back
Kinds of Software Tests
Modified on 11/22/2013 06:06
by
Administrator
Categorized as
Test Fixture Type
,
Test Type
There are many kinds of software tests(many more than listed here) that exercise various aspects of software from the UI down to individual classes and their properties and methods. Some tests focus on just one of [QualityFactors] of software like load testing. Which of the [QualityFactors] are addressed depends on the kind of test. For a more complete list with links to detailed articles check out [http://en.wikipedia.org/wiki/Software_testing#Testing_Types|Wikipedia]. {TOC} ===Unit Testing=== Unit testing is the testing of an individual unit or group of related units. It falls under the class of white box testing. It is often done by the programmer to test that the unit he/she has implemented is producing expected output against given input.{br} [imageauto||{UP(TestKind)}MBTinaNutshell.png|^http://blogs.msdn.com/b/specexplorer/archive/2009/10/27/what-is-model-based-testing.aspx] ===Integration Testing=== Integration testing is testing in which a group of components are combined to produce output. Also, the interaction between software and hardware is tested in integration testing if software and hardware components have any relation. It may fall under both white box testing and black box testing. ===Functional Testing=== Functional testing is the testing to ensure that the specified functionality required in the system requirements works. It falls under the class of black box testing. ===System Testing=== System testing is the testing to ensure that by putting the software in different environments (e.g., Operating Systems) it still works. System testing is done with full system implementation and environment. It falls under the class of black box testing. ===Stress Testing=== Stress testing is the testing to evaluate how system behaves under unfavorable conditions. Testing is conducted at beyond limits of the specifications. It falls under the class of black box testing. Performance Testing Performance testing is the testing to assess the speed and effectiveness of the system and to make sure it is generating results within a specified time as in performance requirements. It falls under the class of black box testing. ===Usability Testing=== Usability testing is performed to the perspective of the client, to evaluate how the GUI is user-friendly? How easily can the client learn? After learning how to use, how proficiently can the client perform? How pleasing is it to use its design? This falls under the class of black box testing. ===Acceptance Testing=== Acceptance testing is often done by the customer to ensure that the delivered product meets the requirements and works as the customer expected. It falls under the class of black box testing. ===Regression Testing=== Regression testing is the testing after modification of a system, component, or a group of related units to ensure that the modification is working correctly and is not damaging or imposing other modules to produce unexpected results. It falls under the class of black box testing. ===Beta Testing=== Beta testing is the testing which is done by end users, a team outside development, or publicly releasing full pre-version of the product which is known as beta version. The aim of beta testing is to cover unexpected errors. It falls under the class of black box testing.
Meta Keywords:
Meta Description:
Change Comment:
ScrewTurn Wiki
version 3.0.5.600. Some of the icons created by
FamFamFam
.