March 18, 2004

Types of Testing

Here is an attempt at a list of the various testing levels:

Concept Testing: Testing to see if the concept of the application is viable.
Functional Testing: Testing if the function that was changed/enhanced works as expected.
Unit Testing: Testing to see if the program still functions as anticipated based upon scenarios.
Data Migration Testing: If you are switching to a new system, this is a test to ensure the data from the old system migrates properly to the new system.
Integrated Testing: Testing to see if the application still functions as anticipated with other applications also based upon scenarios.
Stress Testing: Testing to ascertain the load an application can withstand
Regression Testing Testing to ensure that with the existing software, the newly added component doesn't have a negative impact. Normally scenarios are a good idea here.
Interoperability Testing: Two systems are being tested for the data passed between the systems. Again scenarios are ideal.
Usability Testing: How users interact with the application. Is it cumbersome or does it flow?
User acceptance Testing: The overall process satisfaction by the project sponsor and customers.

Posted by Elyse at March 18, 2004 5:28 AM | TrackBack
Comments

The list is fine. But it has not included the detailed description of test types.

Posted by: vijaya at June 22, 2004 7:37 AM

This is a nice information for who are interested in tesinhg. I have recently dicided to take testing course. Advice me how to prepare for it. Send me if you have any tesing material.
stay in touch by the emails.

Posted by: Shailu at June 22, 2004 12:19 PM

difference between load testing and stress testing

Posted by: magesh at July 6, 2004 10:36 PM

Hi,
Load Testing is "to test the application with usual load that means applicable load and see how the system is working whether it is crashing etc..
stress testing is to test the app. with maximum load i.e unusual load
performance test is test the app. with concurrent users like 100 or 50 then see how much time it takes to get response.

thanks,
madhava

Posted by: KRM at July 7, 2004 4:32 AM

is it possible to know the particular object font size with our expected result

Posted by: karthik at July 14, 2004 4:49 AM

This is a nice information for who are interested in tesinhg. I have recently dicided to take testing course. Advice me how to prepare for it. Send me if you have any tesing material.
stay in touch by the emails.Any way ok.but there r some more testing types r tehere,please specy the othertypes also.please b in touch with me.

thanks

Posted by: rakesh kodali at July 27, 2004 6:32 AM

hi,need agood friend to discuss abt testing tools.so,please mail me.

Posted by: rakesh kodali at July 27, 2004 6:40 AM

BETA TESTING. Testing conducted at one or more customer sites by the end-user of a delivered software product or system.


BLACK BOX TESTING. A testing method where the application under test is viewed as a black box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications. Also known as behavioral testing, since only the external behaviors of the program are evaluated and analyzed.

DATA FLOW TESTING Testing in which test cases are designed based on variable usage within the code.[BCS]


DATABASE TESTING. Check the integrity of database field values

Posted by: rakesh kodali at July 27, 2004 6:56 AM

FUNCTIONAL TESTING Application of test data derived from the specified functional requirements without regard to the final program structure. Also known as black-box testing.

Posted by: rakesh kodali at July 27, 2004 6:57 AM

GRAY BOX TESTING Test designed based on the knowledge of algorithm, internal states, architectures, or other high -level descriptions of the program behavior. [Doug Hoffman]
GRAY BOX TESTING Examines the activity of back-end components during test case execution. Two types of problems that can be encountered during gray-box testing are:
§Ҩi A component encounters a failure of some kind, causing the operation to be aborted. The user interface will typically indicate that an error has occurred.
§Ҩi The test executes in full, but the content of the results is incorrect. Somewhere in the system, a component processed data incorrectly, causing the error in the results.

Posted by: rakesh kodali at July 27, 2004 6:58 AM

there r some materials abt testing,those who need please contact kodalirakesh@yahoo.co.in

Posted by: rakesh kodali at July 27, 2004 6:59 AM

will it be called as interoperability testing when the testing is performed on the application with same database...for example In a railway reservation system we have got number of railway station and let us assume that there is only one seat is left, and two different people form two different destination reserve the ticket. In fact only one should get the ticket… how could we test this function… is this test is called interoperability testing?
Please send me ur openion….

Posted by: romy mathew at September 4, 2004 1:35 AM

hi ayyar!!

This is a good question ...but don't have the correct answer..I think kodali will give the answer..how do u predict or say u r satisfied with the testing schedule??

Posted by: Danny at April 8, 2005 2:27 AM

list without details.

Posted by: abhishek at January 2, 2006 4:11 AM