Tuesday, January 8, 2008

TESTING ACTIVITIES


Testing is a process that is used to identify the correctness, completeness and quality of developed software. Testing is a process that is nothing but deals with criticism and comparing of expected results and the actual results. There are many ways to software testing but the effective way to testing is through the process of investigation. The questioning a product is done in order to evaluate the product. The questions are what the tester tries to do with a product and then notice the behavior of the product.

In practical testing is done through reviews and inspections. In other words testing is also defined as dynamic analysis of the product we are building. The testing process puts emphasis on the on various things like reliability, portability, maintainability, stability and usability of the product.

The various activities are as follows:

1. unit testing

2. integration testing

3. system testing

UNIT TESTING: This kind of testing is testing which is done at lower level. Unit testing is done at end of formation of each module. Unit testing is a procedure of verifying the module of source code. The idea behind unit testing is to write test cases and functions so that whenever changes causes regression then it can be quickly picked and identified.

BENEFITS :

  • Unit testing facilitates changes in the system.
  • Unit testing provides a brief documentation at the end of formation of each module.
  • Unit testing simplifies integration.

LIMITATIONS:

· Unit testing does not catch every error in the program.

· It does not deal with findings of integration error, performance error, and system wide issues.

INTEGRATION TESTING:

Integration testing deals with with finding of inconsistencies in the part of program module. The integration testing deals with the interface problems. This type of testing deals with the fact that one module is able to interact with the other module of the system or not. In this kind of testing both the hardware elements and the software elements are combined and tested until they are properly integrated with each other.

Sometimes integration testing is also called as system testing

SYSTEM TESTING:

1. System testing is conducted on a complete integrated system to identify that whether the built system is able to meet the client’s requirements or not. If the results of the system are not met with the requirements of the clients then the system fails.

2. System testing falls with scope of BLACK BOX testing since we don’t concentrate on the internal logic of the system.

3. In system testing we don’t need to concentrate that what inputs we are using and what processing needs are.

4 We just lay emphasis on whether the system is meeting the client’s requirements or not.

There are some other kinds of testing as given below.

REGRESSION TESTING:

This testing is done to ensure that applied changes made is not adversely affecting the

functionality of previous tested modules.

PERFORMANCE TESTING:

This testing makes sure that the application performs to the customer expectation in terms of response time, portability, scalability.

Performance testing deals with identifying that the application is able to meet its performance criteria.

It also lay emphasis on how fast a system works under a particular workload.

STRESS TESTING

In stress testing we deal with a fact that how much load an application is able to handle in particular condition.

The stress testing tries to check the stability of a system.

The testing tries to check the software beyond normal operational conditions or even to the level of break point state

No comments: