A Strategic Approach to Software Testing

This paper provide a precise summery of a survey of software testing approach and technique. This reviews some of the common approaches in the integration testing of object – oriented program are also included. It helps in evaluating the effectiveness of testing by providing data on different coverage items. Different keywords were defined as a search string based on the research questions. These include Code Coverage, Software Testing, Prototype Testing, and Traceability. In this paper on the basis of current researches on software testing and preexisting approach of software strategy is described. Software is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation. Software is tested from two different perspectives one, Internal program logic is exercised using ‘white box or glass box’ test case design technique second, software requirement are exercised using ‘black box’ test case design technique. This paper provides a study of current test coverage researches conducted by the other researches for test coverage in software testing. Testing is very important activity in software development process. It is to examine and modify source code. This paper deals with a significant and important issue of testing. It is conducted basically manually as well as automated both have their own merits and demerits. Testing automation tools enables developers and testers to easily automate the entire process of testing in software development. This paper includes description about automated Testing tool such as Test Complete. KEYWORD; SQA, Testing Technique, V&V, Testing Levels, FSM, Test Case Design. INTRODUCTION: Today, every company has mechanism to ensure quality by applying solid technical methods are measures, and performing well planed software testing technique. The 1388 Keertika Singh, Sumit Kumar Mishra, Gaurav Shrivastava study presented here is that the latest research and issues on software testing [1]. SOFTWARE TESTING TECHNIQUE: Fundamental Principal of Testing: The objective of the testing is to provide a quality product to the customer [2]. 1. The goal of testing is to find defects before customers find them out. 2. Exhaustive testing is not possible; program testing can only show the presence of defects, never their absence. 3. Testing applies all through the software life cycle and is not an end ofcycle activity. 4. Understand the reason behind the test. 5. Test the tests first. Testing Objective: The main objective of testing is1. 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 high probability of finding an as-yetundiscovered error. 3. A successful test is one that uncovers an as-yet-undiscovered error. [3] TYPE OF TESTING APPROACH Verification and Validation approach: Verification refers to the set of activities that ensure that software correctly implements a specific function. Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements [4, 5]. Verification: "Are we building the product right?" Validation: "Are we building the right product? Levels of Testing: Unit level Procedure: Unit is the smallest part of a software system which is testable it may include code files, classes and methods which can be tested individual for correctness. Unit is a process of validating such small building block of a complex system, much before testing an integrated large module or the system as a whole. Driver and/or stub software must be developed for each unit test A driver is nothing more than a "main program" that accepts test case data, passes such data to the component, and prints relevant results. Stubs serve to replace modules that are subordinate (called by) the component to be tested. A stub or "dummy subprogram" uses the subordinate module's interface. Integration Testing: Integration is defined as a set of integration amoung component. Testing the A Strategic Approach to Software Testing 1389 interactions between the module and interactions with other system externally is called Integration Testing. Type of Integration Testing  Top-down Integration  Bottom-up Integration  Regression Testing