next up previous contents
Next: FileIO module testing Up: Module testing reports Previous: DTWLIB.DLL testing results   Contents

Plotter testing results

Horizontal plotter

M-HP-01:

Testing logged and screenshots taken. Testing output files in testing\M-HP-01 directory.

  1. Exception caught on DTWHorizontalPlotter.paint(). No exception handling for zero values in ``values'' -array
  2. No exceptions, but no plotting drawn. Screenshot in OneValue.jpg
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-HP-02:

Testing logged and screenshots taken. Testing output files in testing\M-HP-02 directory.

  1. Exception caught.
  2. No plotting drawn.
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but it is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-HP-03:

Testing logged and screenshots taken. Testing output files in testing\M-HP-03 directory.

  1. Exception caught.
  2. No plotting drawn.
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but it is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-HP-04:

Testing data logged and screenshots taken. Testing output files in testing\M-HP-04 directory. Testing results were as expected.

M-HP-05:

Testing data logged and screenshots taken. Testing output files in testing\M-HP-05 directory. Testing results were as expected.

Vertical plotter

M-VP-01:

Testing logged and screenshots taken. Testing output files in testing\M-VP-01 directory.

  1. Exception caught on DTWHorizontalPlotter.paint(). No exception handling for zero values in ``values'' -array
  2. No exceptions, but no plotting drawn.
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-VP-02:

Testing logged and screenshots taken. Testing output files in testing\M-VP-02 directory.

  1. Exception caught.
  2. No plotting drawn. Screenshot in OneValue.jpg
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but it is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-VP-03:

Testing logged and screenshots taken. Testing output files in testing\M-VP-03 directory.

  1. Exception caught.
  2. No plotting drawn. Screenshot in OneValue.jpg
  3. Plotting drawn. Screenshot in MoreValues.jpg
  4. Plotting drawn, but it is not clear. Screenshot in TooManyValues.jpg
Testing results were as expected. Errors causing exceptions were fixed during testing.

M-VP-04:

Testing data logged and screenshots taken. Testing output files in testing\M-VP-04 directory. Testing results were as expected.

M-VP-05:

Testing data logged and screenshots taken. Testing output files in testing\M-VP-05 directory. Testing results were as expected.

Selection plotter

M-SP-01:

Getting negative selections failed with an exception. Getting selections with too big indeces resulted in an exception. Selections limited, so negative and too large indeces are not possible. Limited selection lenght to a minimum of three items. After fixing these problems the module's behaviour was similar to expected.

Path plotter

M-PP-01:

Testing results were similar to the expected values for the test case.

All function points of the plotter modules were tested. The testing was done to cover all normal use of the modules. Code coverage of the testing can be estimated to reach over 95% of the code.


next up previous contents
Next: FileIO module testing Up: Module testing reports Previous: DTWLIB.DLL testing results   Contents
2002-03-19