Static Test Cases And The Dynamic Test Runs

by Nataliia Vasylyna | January 25, 2012 10:00 am

As soon as testing models have been built and validated, they can be used to create test cases, which may then be implemented planned test procedure.

So, let us start!

First of all it is necessary to determine and recognize the static test cases and the dynamic test runs.

Well, a test case[1] is an accumulation of points and related data that permits a test to be implemented or a test run to be conducted.

In turn, a test run is a dynamic unit of specific test activities in the general testing progression on a particular testing object.

Every time a static test case is invoked, we have an individual dynamic test run. In such a way every test case can correspond to multiple test runs.

The data containing in a test case should allow the related test run to start, continue, and finish. In many cases the beginning and ending aspects correspond to the initiation and termination of the operations for the total software system.

Among the test case data is the specific input to the software object in operation, which comprises both the primary input at the start of the test run and the input to permit it to persist and to finish.

The test case often comprises data about the anticipated result throughout the test run, which determines the program behavior under this test run. Such input, output and timing data can be captured by the set of input variables, the set of output variables, and their values over time.

Sometimes test cases may be derived straight from other sources. For instance, actual runs from in-field operations of software may sometimes be used to conduct test runs. In this case, a strategy of record-and-rep1ay is used.

For some systems if the needed data is easy to get this strategy might be very effectual.

On the other hand, for the majority of big systems, too much information might need to be recorded, making this strategy impractical. Systematic analysis of recorded data may provide valuable insight into the usage situations of the product. Systematic models built using such recorded data may provide more efficient ways to conduct software testing than just playing back the recorded runs.

Learn more from QATestLab

Related Posts:

  1. test case:
  2. 4 Attributes of Qualitative and Well-Written Test-Case:
  3. How to prepare for Winter Sales:
  4. What is Data Migration Testing:

Source URL: