Features and Capabilities of Test Data Design and Test Data Creation

Test Case Design

  • QA can learn to detect ambiguous specifications, incomplete specifications, and logically inconsistent specifications long before code is generated.
  • QA can learn to create a more consistent level of high quality testing independent of the overall experience level of the tester.
  • Testers can generate mathematically equivalent test cases to the set of functionality in all of the specifications.
  • QA can receive assistance from RBT produced test cases that can factor in potential defects that can cancel each other out resulting in getting the right answer for the wrong reason.
  • QA can view a comprehensive logic diagram to identify where diagnostic probe points should be inserted in the code for more accurate testing
  • Provides QA with an optimized test library with the opportunity to identify twice the coverage for half the test cases.
  • QA to receive information from RBT and its ability to identify generated test cases that will cover 80 to 90% of the code significantly shortening the time toachieve the 100% statement of branch coverage.
  • QA can receive a set of negative tests as well as the full set of “go right” tests.
  • Consistent test cases are available in describing the various inputs and outputs of the test (i.e., if the same variable at the same state is part of the inputs/outputs of more than one test, it will always be described by RBT in exactly the same way).
  • QA can learn a cause-effect graphing process that helps identify system integration issues before design completion.
  • Flexible test design approaches with addition of Quick Design
  • Full constraint processing
  • QA can determine what changes need to be made to existing tests when the
    application’s rules change.

Test Coverage Measurement

  • QA can quantify the functional test coverage based on what test cases passed and failed.
  • A subset of tests can be identified with maximum coverage.

Test Exporting

  • QA can export the test descriptions to test management tools.
  • QA can export the test descriptions to most of the major playback tools in the form of comments in shell scripts. This helps create self- documenting tests saving scripting time.
  • QA can export the test data to Excel via a comma delimited file

Test Document Generation

  • QA can generate ancillary documentation information that may be necessary which saves testers a great deal of time.
  • QA can generate test cases in various formats in batch mode, script mode, and DOD 498 format.

Test Coverage Analysis

  • Stakeholders can protect the investment in test cases already built, whether designed by RBT in a prior release or done independently of RBT.
  • Testers can run “What if “scenarios for functional coverage that can be used to determine the optimal subset of test cases to build.

Requirements Management Integration

  • Relationships between system specifications and test specifications are
    available.
  • Users can view RBT test cases from a requirements management tool.
  • Users can view the status of the most current successful functional test
    coverage.

Requirements Based Testing Process

  • QA can learn a full process for testing the specifications.
  • Stakeholders can be involved in Ambiguity Review training that can help in uncovering numerous classes of defects in the specifications at reading pace.
  • QA can learn and use Cause-Effect Graphing steps that when applied by the
    testers can help identify more subtle issues with the specifications.

Read our white paper on achieving maximum code coverage.

See us in action, Register for a Webinar or a Live Demo.

 

Contact Grid-Tools