Testing Methods

Testing Strategies

Testing software is a critical element of software quality assurance and represents the ultimate review of specification; and coding software testing fundamentals define the overriding objectives for software testing.

TESTING OBJECTIVES

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

Ø  A good case is one that has a high probability of finding an error.

Ø  A successful test is one that uncovers a yet undiscovered error. If testing is conducted successfully it will uncover errors in the software. Testing cannot show the absence of defects, it can only show the software defects are present.

TESTING PRINCIPLES

Before applying methods to design effective test cases, a software engineer must understand the basic principles that guide e software testing.

Ø  All tests should be traceable to customer requirements.

Ø  Test should be planned long before testing begins.

Ø  Testing should begin “in small” and progress towards testing “in large”

Ø  Exhaustive testing is not possible.

Ø  To be most effective. An independent third party should conduct testing.

TESTING TECHNIQUES

The primary objective for test case is to drive a set of sets that has the highest likelihood for uncovering defects in the software. Testing is the process of executing a program with the intent of finding as a yet and discovered error. To accomplish this objective tow different categories of test case technique used.

After test plan and before going to test design test case is important. According to the project requirements we have to test some conditions to ensure the quality of software. For the purpose of testing these conditions we have to write test cases.

TESTING STRATEGIES

Testing is a set of activities that can be planned in advance and connected systematically. A strategy for software testing must accommodate low level tests that are necessary to verify a small source code segment has been correctly implemented as well as high level tests that validate system functions against customer requirements.

                                      

 TEST CASE PREPARATION

1.1 BLACK BOX TESTING

The concept of the black box is used to represent a system whose inside workings or no available for inspection. In a black box, the test item is treated as a “black” since its logic is unknown: all that is known is what goes in and what comes out, or the input and output. Here, in this “Electronic Management Information System” the internal functionalities have been tested.

1.2 WHITE BOX TESTING

White box testing assumes that the specific logic is important and must be tested to guarantee the system’s proper functioning. The main use of the white box testing is in error based testing.

It is predict on close examination of procedural detail logical providing test cases that exercise specific sets of conditions and/or loops test path enough the software. Basis path testing is a white box testing technique. The basis path method enables the test case designer to derive a logical complexity of a procedural design and use this measure as a guide for defining as basis set of execution path.

 TEST CASE VERIFICATION

1. UNIT TESTING

Unit testing focuses on verifying the effort on the smallest unit of software-module. The local data structure is examined to ensure that the date stored temporarily maintains its integrity during all steps in the algorithm’s execution. Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing.

2. INTEGRATION TESTING

Data can be tested across an interface. One module can have an inadvertent, adverse effect on the other. Integration testing is a systematic technique for constructing a program structure while conducting tests to uncover errors associated with interring.

3. PERFORMANCE TESTING

Performance Testing is used to test runtime performance of software within the context of an integrated system. Performance test are often coupled with stress testing and require both software instrumentation

 VALIDATION TESTING

After performing the validation testing, the next step is output testing of the proposed system since no system would be termed as useful until it does produce the required output in the specified format. Output format is considered in two ways, the screen format and the printer format.

 SYSTEM TESTING

System Testing is nothing but the testing the entire system. The following test cases are coming from the system testing.