Basics of Software Testing.pptVIP

Basics of Software Testing Contents Fundamentals of Software Testing Test Case Design Testing Techniques Black Box White Box Control Structure Testing for Special Environments GUI Environment Real-Time System Testing Strategies Unit Testing Integration Testing Validation Testing System Testing Fundamentals of Software Testing Fundamentals of Software Testing The development of software systems involves a series of development activities where opportunities for injection of human errors are enormous. Errors may begin to occur at the very early stages of SDLC. Software Testing is a process to find these errors. Software testing is a critical element of software quality assurance and represents the review of specification, design, and code generation. Some of the testing objectives are as follows: Testing is a process of executing a program with the intent of finding an error. A good test case is one that has a high probability of finding an as-yet undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error. Before applying methods to design effective test cases, a software engineer must understand the basic principles that guide software testing. Testing principles that have been widely adapted are as follows: All tests should be traceable to customer requirements. The objective of software testing is to uncover errors. It follows that the most severe defects (from the customer’s point of view) are those that cause the program to fail to meet its requirements. Tests should be planned long before testing begins. Test planning can begin as soon as the requirements model is complete. Detailed definition of test cases can begin as soon as the design model has been solidified. Therefore, all tests can be planned and designed before any code has been generated. The Pareto principle applies to software testing. Stated simply, the Pareto principle implies that 80 percent of all errors uncovered during testing will likely be tracea