Software testing and its objectives

Software Testing

Software testing is the process of executing a pro ram with the intention of finding errors. It is a process to verify that whether a system or its parts is satisfying specified requirements or not.
Following are the objectives es of software testing:
1. Software quality improvement
2. Verification and validation
3. Software reliability estimation

1. Software quality improvement:

Software quality means conformance to the specified software design requirements. The minimum requirement of quality means performing as required under specified circumstances. Software testing is not only uses to remove bugs but also to find out design defects by the programmer.

2. Verification and validation:

Verification means to test that we are building the product in right using a are the correct procedure for the development of software so that it can meet the user requirements. Whereas validation is the process which checks that whether we are building the right product or not.

3. Software reliability estimation

Software reliability has an important relationship with many aspects of software development. Its objective is to discover the residual designing errors before delivery to the customer. The failure data during the testing process are take down in order to estimate the software reliability.

Principles of Software testing

1. All tests should be traceable to customer requirements.
2. Testing time and resources are in limit, so avoid the redundant test.
3. It is impossible to test everything.
4. Use effective resources to test.
5. Test should be planned long before testing begins i.e., after the requirement phase.

Unit / Module testing

1. The Unit testing is a level of software testing where individual units/ components of the software are testing.
2. Unit testing focuses verification effort on the smallest unit of software design, the software component or module.
3. In unit testing, individual components are testing to ensure that they are working properly in the same manner as required.
4. In this process, a module (software component) is taken and executed in isolation from the rest of the software product. That’s why it is also called “software component testing”.
5. It is the lowest level of testing of an application.
6. The relative complexity of tests and uncovered errors is limiting by the constrained scope established for unit testing.
7. The unit testing is white box oriented. And the steps can be conduct in parallel or multiple components.
8. Unit testing is typically conducting by the development team and programmer who coded the unit.

Read more about the Information model