Software Testing IN OCS

Software Testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding, Testing presents an interesting anomaly for the software engineer.

Testing Objectives include

1.                             Testing is a process of executing a program with the intent of finding an error

2.                             A good test case is one that has a probability of finding an as yet undiscovered error

3.                             A successful test is one that uncovers an undiscovered error

Testing Principles

1.     All tests should be traceable to end user requirements

2.     Tests should be planned long before testing begins

3.     Testing should begin on a small scale and progress towards testing in large

4.     Exhaustive testing is not possible

5.     To be most effective testing should be conducted by a independent third party

 Structural Testing(white box)

          White box testing assumes that the specific logic is imported and must be tested to guarantee the system’s proper functioning. The main use of the white box is in error - based testing, when you already have tested all objects of an application and all external or public methods of an object of an application that you believe is of grater importance.

          One form of white box testing, called path testing, make certain that each path in an object’s method is executed at least once during testing.two types of path testing are statements testing coverageand branch testing coverage.

 Statements testing coverage: The main idea of statement testing coverage is to test every statement in the objects by executing it at least once.

 Brach testing coverage: the main idea behind branch testing coverage is to perform enough tests to ensure that every branch alternative has been executed at least once under some test.

 Functional Testing (Black Box)

           The concept of black box is used to represent a system whose inside working are not available for inspection. In a black box the test item is treated as ‘black’, since its logic is unknown is what goes in and what comes out, or the input and output.

          In Black box testing, you try various inputs and examine the resulting output. The black box testing technique can be used for scenario based tests, where the system inside may not be available for inspection but the input and output are defined through use cases or other analysis information.