Testing

                                                       Testing

In the testing phase the system is tested for its efficiency.

Under this process, a system is provided with a set of test cases and is observed if the system behaves as expected. The aim of this phase is to make the final product free of errors.

During this phase the system is tested multiple times with different set of inputs. If the output is erroneous, the system is analyzed and debugged, which helps in detecting where the trouble is with the module. If there is any trouble, then it is fixed and again tested.

Testing is done in two phases: Unit testing & System testing.

 Black-box  testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings (see white-box testing). Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. The tester is only aware of what the software is supposed to do, but not how i.e. when he enters a certain input, he gets a certain output; without being aware of how the output was produced in the first place

Black box testing attempts to find

                errors in the following categories:

ü  Incorrect or missing functions

ü  Interface errors

ü  Errors in data structure or external data base access

ü  Performance errors

ü  Initialization and termination errors

ü  Unlike white box testing, which is performed early

                                   in the testing process? Black box testing tends

                                  to be applied during later stages of testing.

                                   Because of Black Box Testing

               Tests are designed to answer the following questions:

Ø  How is functional validity tested?

Ø  What class of input will make good test cases?

Ø  Is the system particularly sensitive to certain input values?

Ø  How are the boundaries of a data class isolated?

Ø  What effect will specific combinations of data have on system operation?

 White-box testing  : -  white box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing). In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases.

Using White Box Testing method the

tests cases that can derive are:

                All independent paths with in a module have been

                exercised at least once.Exercised all logical decisions

                their true or false side.Execute all loops at their

                boundaries and within their operational bounds.

                Exercise internal data structures to ensure their validity.

    

Unit testing: - Each function in the system is tested independently for error detection and correction thereof. The end product of this phase is the functions that have been tested individually.

                                                   In our project first we test all function/ module individually, in this testing we find out the error on display customer Details module. Here this page is do not display sex of customer.

Integration testing :- Integration testing can be either black box or white box testing. Black box testing is testing where the person designing the test has no (or very little) internal knowledge of the system they are testing. White box testing, also known as glass box or clear box testing, is testing that takes place where the tester has working knowledge of the code, technology, and architecture.

 Verification and validation  :-  Verification and validation testing are two important tests, which are carried out on a software, before it has been handed over to the customer. This makes sure, that the software testing life cycle starts early. The aim of both verification and validation is to ensure that the software product is made according to the requirements of the client and does indeed fulfill the intended purpose. So that the software product is tested thoroughly without any bias, often the job of validation testing may also be given to third party validation testing services. Therefore, validation testing is an important part of software quality assurance procedures and standards.

System testing: - The modules that were unit tested in earlier phase are integrated and then system testing is carried out. The purpose of system testing is to ensure that the developed system functions according to the requirements.

The development phase of a project is not complete without testing the system.