PathParserFailureTest

Overview

Package

Class

Use

Deprecated

Index

Home >> All >> org >> apache >> batik >> [ parser overview ]

PREV CLASS NEXT CLASS

SUMMARY:

JAVADOC |

Sourc code of org.apache.batik.parser.PathParserFailureTest

SOURCE |

Download org.apache.batik.parser.PathParserFailureTest

DOWNLOAD | NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

org.apache.batik.parser
Class PathParserFailureTest

java.lang.Object
  org.apache.batik.test.AbstractTest
      org.apache.batik.parser.PathParserFailureTest

All Implemented Interfaces:: org.apache.batik.test.Test

public class PathParserFailureTest
extends org.apache.batik.test.AbstractTest

To test the path parser.

Version:: $Id: PathParserFailureTest.java,v 1.3 2004/08/18 07:16:42 vhardy Exp $

Field Summary

protected java.lang.String sourcePath


Fields inherited from class org.apache.batik.test.AbstractTest

id, name, parent

Constructor Summary

PathParserFailureTest(java.lang.String spath)
          Creates a new PathParserFailureTest.

Method Summary

org.apache.batik.test.TestReport runImpl()
          Subclasses should implement this method with the content of the test case.

Methods inherited from class org.apache.batik.test.AbstractTest

assertEquals, assertEquals, assertNull, assertTrue, error, getId, getName, getParent, getQualifiedId, reportError, reportException, reportSuccess, run, runImplBasic, setId, setName, setParent

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

sourcePath

protected java.lang.String sourcePath

Constructor Detail

PathParserFailureTest

public PathParserFailureTest(java.lang.String spath)

Creates a new PathParserFailureTest.

Method Detail

runImpl

public org.apache.batik.test.TestReport runImpl()
                                         throws java.lang.Exception

Description copied from class: org.apache.batik.test.AbstractTest

Subclasses should implement this method with the content of the test case. Typically, implementations will choose to catch and process all exceptions and error conditions they are looking for in the code they exercise but will let exceptions due to their own processing propagate.