SQAtester.com   your software testing reference on line     Test Run Planning     You are here: Home Testing Center SQA Course Black Box Testing Bugs and Fixes Test Run Planning Test runs are based on the application requirements to be tested. One of the most important attributes of test run execution is that it be repeatable. To facilitate application changes and problem resolution, it is critical that a test produces the same results each time it is executed. Test components must be available and maintained to allow repeatable execution of a test. A complete documentation trail must be maintained and all file control processes must be observed to achieve this. Unit Test The developer designs unit test runs to exercise and validate a code unit's logic, and to verify a code unit's compliance with requirements specifications at the code unit level. Integration Test Runs The goal of integration testing is to verify that all client requirements have been met and that all internal and external interfaces work. The achievement of these goals is facilitated by using builds as part of the integration test strategy. Low-level utility, high risk, or prototype code units should be implemented first even though the build approach is primarily top-down. Acceptance Testing Is the process of comparing a program to its requirements. These are test runs for the builds needed to test the first software deliverables as defined in Test Plan. Regression Test Runs Regression testing is designed to ensure that maintenance activities do not introduce new errors into code. When planning regression testing for maintenance, it is a good idea to plan to run the highest level builds representing the most complex test cases first. Multiple strategies for grouping test data into test files must be pursued at a detailed test run level. Strategies include grouping by characteristics such as: Strategy Example Functionally related requirements Test entry of all fields for adding a customer Screen/window validation Verify design compliance and conformance to standards Navigation Verify navigation between windows. Exercise function key usage. Valid data. Add a valid customer to the Customer Database. Invalid data. Test cross-field validation logic.Enter all combinations of inconsistent data values and mutually exclusive fields. No data. Run New Customers Report with empty New Customers file Technical requirements, such as stress, volume, performance. All the above, run in stress ( validate software functionality at the limit ), volume (process of feeding a program with heavy volume of data. ), performance ( Measurement and prediction of performance )conditions.     Related Links: Books, Magazines, Software, SQA, Y2K Resources Bugs and Fixes Bugs Life Bug Tracking Chat Room Companies and Products Documentation and Strategy More Resources Publications and News Resume Bank Software Life Cycle Test Methodology and Techniques Testing Newsletter Tips and Hints Tools and Automation Tutorials and Training Job Search QA and Developers Testing Center   Copyright © Allka, Co. 1999 For information on SQAtester.com, visit About Us