All Packages from org.apache.batik.test.svg.* to org.apache.batik.test.xml.*

Home >> All >> org >> apache >> batik >> [ test Javadoc ]

•

• org.apache.batik.test: Javadoc index of package org.apache.batik.test.

Package Samples:

• org.apache.batik.test.xml
• org.apache.batik.test.util
• org.apache.batik.test.svg

Classes:

• AbstractTest: Base class containing convenience methods for writing tests. There are at least three approaches to write new tests derived from AbstractTest : You can simply override the runImplBase method and return true or false depending on whether or not the test fails. You can choose to report more complex test failure conditions by overriding the runImpl method which returns a TestReport . In that case, you can use the convenience methods such as reportFailure reportSuccess or reportException to help build a TestReport , and use the TestReport 's addDescriptionEntry to populate the report with relevant ...
• TestReportValidator: This Test implementation can be used to validate the operation of a specific test. A typical use is to create known error conditions and check that the input Test reports these errors properly. This test checks that a given test status (passed or not) and a given error code is returned by a Test . A TestReportValidator is built with the Test to run, the expected status (passed or failed) and the expected error code. The TestReportValidator will pass if the expected values are produced by the TestReport created by the associated Test . Otherwise, it will fail with one of two error codes: + if the ...
• SelfContainedSVGOnLoadTest: This test takes an SVG file as an input. It processes the input SVG (meaning it turns it into a GVT tree) and then dispatches the 'onload' event. The SVG input file should contain script that will position the result of the test in the DOM using the following namespace: xmlns:test="http://xml.apache.org/batik/test" The result should be set in the result attribute of the <testResult> element by the script embeded in the input SVG test file. Sample input SVG file: <svg ... onload="runTest(evt)" xmlns:test="http://xml.apache.org/batik/test" > <script type="text/ecmascript"> function ...
• SVGOnLoadExceptionTest: This test takes an SVG file as an input. It processes the input SVG (meaning it turns it into a GVT tree) and then dispatches the 'onload' event. In that process, the test checks for the occurence of a specific exception type and, for BridgeExceptions, for a given error code. If an exception of the given type (and, optionally, code) happens, then the test passes. If an exception of an unexpected type (or code, for BridgeExceptions) happens, or if no exception happens, the test fails. The following properties control the test's operation: - Scripts: list of allowed script types (e.g., "application/java-archive") ...
• XMLTestSuiteRunnerValidator: Validates the operation of the XMLTestSuireRunner by checking that it runs the tests specified by the command line parameter and only these tests. The test uses an dummy <testRun> which contains: - testRun, id="all" - testSuite, href="testSuiteA.xml" - testSuite, href="testSuiteB.xml" Where: - testSuite, id="A" - test, id="A1" - test, id="A2" - test, id="duplicateId" - testGroup, id="AG" - test, id="AG1" - test, id="AG2" and: - testSuite, id="B" - test, id="B1" - test, id="B2" - test, id="B3" - test, id="duplicateId" where all the leaf test pass.
• XMLTestSuiteRunner: This class can be used to build and run a TestSuite from an XML description following the "XML Test Run" and "XML Test Suite" formats, whose constants are defined in the XTRunConstants and XTSConstants interfaces. This class takes a "Test Run" XML description as an input. That description contains: + pointers to a number of "Test Suite" XML descriptions, which contain the definition of the set of Tests to be run and their configuration. + a description of the set of TestReportProcessor and their configuration that should be used to process the reports generated by the various TestSuites .
• PerformanceTest: This abstract Test implementation instruments performance testing. Derived classes need only implement the runOp and, optionally, the runRef methods. The setReferenceScore method is used to specify the last recorded score for the performance test and the setAllowedScoreDeviation method is used to specify the allowed deviation from the reference score.
• XMLTestReportProcessor: This implementation of the TestReportProcessor interface converts the TestReports it processes into an XML document that it outputs in a directory. The directory used by the object can be configured at creation time. The XMLTestReportProcessor can optionally notify a report consumer of the XML file it created.
• Test: Defines the interface of a Test case. It is highly recommended that implementations derive from the AbstractTest class or follow the same implementation approach, so that no exception is thrown from the run method, which is critical for the operation of the test infrastructure.
• SelfContainedSVGOnLoadTestValidator: This test validates the operation of SelfContainedSVGOnLoadTest. It is a test agregation which points to several tests which correspond to expected error conditions. The test simply validates that the expected error conditions are properly detected and reported.
• SVGRenderingAccuracyTest: Checks for regressions in rendering a specific SVG document. The Test will rasterize and SVG document and compare it to a reference image. The test passes if the rasterized SVG and the reference image match exactly (i.e., all pixel values are the same).
• AbstractRenderingAccuracyTest: Checks for regressions in rendering a specific SVG document. The Test will rasterize and SVG document and compare it to a reference image. The test passes if the rasterized SVG and the reference image match exactly (i.e., all pixel values are the same).
• SimpleTestRunner: Simple GUI tool to run a Test . This tool takes a class name parameter as an input and provides a GUI to run an instance of the test. The generated TestReport is printed to the standard output with the SimpleTestReportProcessor
• SVGAccuracyTestProcessor: This implementation of the TestReportProcessor interface converts the TestReports it processes into an XML document that it outputs in a directory. The directory used by the object can be configured at creation time.
• TestReportProcessor: Interface for classes that can process TestReport instances This allows different applications to use the same TestReport for different purposes, such as generating an XML output or emailing a test result summary.
• XSLXMLReportConsumer: This implementation of the XMLTestReportProcessor.XMLReportConsumer interface simply applies an XSL transformation to the input XML file and stores the result in a configurable directory.
• ImageCompareTest: This test does a pixel comparison of two images and passes if the two images are identical. It fails otherwise, producing a report describing why the two images are different.
• TestSuite: A TestSuite is a composite test, that is, a test made of multiple children Test cases. Running a TestSuite will simply run the children test cases.
• SVGRenderingAccuracyTestValidator: Validates the operation of SVGRenderingAccuracyTest by forcing specific test case situations and checking that they are handled properly by the class.
• ParametrizedTest: This test validates that test properties are inherited from the class that defines the "class" attribute down to each test instance that uses the same class.
• AbstractTestSuite: This class provides an implementation for the addTest method and a protected member to store the children Test instances.
• SimpleTestReportProcessor: A simple implementation of the TestReportProcessor interface that prints out the TestReport to the standard output.

Home | Contact Us | Privacy Policy | Terms of Service