6.1 Testing Principles

6.1 Testing Principle

Following are the testing principles, which are used: The role of a test plan is to guide all testing activities. It defines what is to be tested and what is to be overlooked, how the testing is to be performed (described on a general level) and by whom. It is therefore a managerial document, not technical one - in essence; it is a project plan for testing. Therefore, the target audience of the plan should be a manager with a decent grasp of the technical issues involved. You can find information about test plans in the lecture notes, as well as international standards and textbooks.

Testability: Software testability is simply how easily a computer program can be tested. The checklist that follows provides a set of characteristics
White Box Testing:

White-box testing of software is predicated on close examination of procedural detail. Logical paths through the software are tested by providing test cases that exercise specific sets of conditions and/ loops. A limited number of logical paths can be selected and exercised. Important data structures can be probed for validity. Whit-box also sometimes called glass box testing is a design method that uses the control structure of procedural design to derive test cases.

Advantages of White box testing are:

a) The other advantage of white box testing is that it helps in optimizing the code b) As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testing the application effectively. c) It helps in removing the extra lines of code, which can bring in hidden defects.

Disadvantages of White box testing are:

a) As knowledge of code and internal structure is a prerequisite, a skilled tester is needed to carry out this type of testing, which increases the cost.
b) And it is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the
Behavior or performance errors

5. Initialization and terminal errors

Black-box testing is implementing on our project through test each and every independent.php file. For dependent files, we check the dependency and interface after integrating all the files. For behavior or performance testing we first made demo give it to our project guide and some employees to use and check performance.
3. Testing Strategies:

A strategy provides a road map that describes the step to be undertaken, and how much effort, time and resources will be required. A testing strategy must incorporate test planning, test design, test execution, and resultant data collection and evaluation. The testing strategy followed by us constituted the following component parts as: To accomplish this there are some methods defined. They are: Equivalence Partitioning:

This method divides the input domain of a program into classes of data from which test cases can be derived. These classes, known as Equivalence Classes, represent a set of valid or invalid input conditions. It helps in a manner that one test case alone uncovers number of errors that might otherwise require more number of