Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Test cases planning


Published on

Test cases planning

Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this

Test cases planning

  1. 1. Test Cases Planning  Carefully and methodically planning test cases is a step in that direction. Doing so is very important for four reasons: – – – – Organization. Repeatability. Tracking. Proof of testing (or not testing).
  2. 2. Test Design  IEEE 829 states that the test design specification "refines the test approach [defined in the test plan] and identifies the features to be covered by the design and its associated tests. It also identifies the test cases and test procedures, if any, required to accomplish the testing and specifies the feature pass/fail criteria."
  3. 3. Test cases   the details of a test case should explain exactly what values or conditions will be sent to the software and what result is expected: The IEEE 829 standard also lists some other important information that should be included: – – – Identifiers. A unique identifier is referenced by the test design specs and the test procedure specs. Test item. This describes the detailed feature, code module, and so on that's being tested. Input specification. This specification lists all the inputs or conditions given to the software to execute the test case.
  4. 4. Test cases – – – – Output specification. This describes the result you expect from executing the test case. Environmental needs. Environmental needs are the hardware, software, test tools, facilities, staff, and so on that are necessary to run the test case. Special procedural requirements. This section describes anything unusual that must be done to perform the test. Inter-case dependencies. If a test case depends on another test case or might be affected by another, that information should go here.
  5. 5. Test Procedures  IEEE 829 states that the test procedure specification  "identifies all the steps required to operate the system and exercise the specified test cases in order to implement the associated test design."
  6. 6. Test Procedures  the step-by-step details of exactly how to perform the test cases: – – – Identifier. A unique identifier that ties the test procedure to the associated test cases and test design. Purpose. The purpose of the procedure and reference to the test cases that it will execute. Special requirements. Other procedures, special testing skills, or special equipment needed to run the procedure.
  7. 7. Test Procedures – Procedure steps. Detailed description of how the tests are to be run:           Log. Tells how and by what method the results and observations will be recorded. Setup. Explains how to prepare for the test. Start. Explains the steps used to start the test. Procedure. Describes the steps used to run the tests. Measure. Describes how the results are to be determined for example, with a stopwatch or visual determination. Shut down. Explains the steps for suspending the test for unexpected reasons. Restart. Tells the tester how to pick up the test at a certain point if there's a failure or after shutting down. Stop. Describes the steps for an orderly halt to the test. Wrap up. Explains how to restore the environment to its pre-test condition. Contingencies. Explains what to do if things don't go as planned.