WebCGM 2.1 Test Suite

This version
http://www.w3.org/Graphics/WebCGM/2009/WebCGM21/testsuite21.html
Latest revision date
15 December 2009.
Editor
Lofton Henderson

Copyright 2009 W3C (MIT, ERCIM, Keio), and OASIS. All Rights Reserved. W3C liability, trademark and document use rules apply.


Summary

The public WebCGM 2.1 Test Suite was designed to validate the WebCGM 2.1 specification and to insure that all features in the WebCGM 2.1 specification are implementable. WebCGM 2.1 uses the conventional criterion for implementable - the feature has been implemented at least twice by implementations developed independently by different organizations.

The WebCGM 2.1 Test Suite is maintained by the OASIS WebCGM TC.

This WebCGM 2.1 Test Suite adds tests to the ~300 tests of the WebCGM 2.0 Test Suite.

The CGM Open Test Suite covers all WebCGM 2.1 features. It covers the new Style Property additions to the WebCGM DOM/ XCF, the new ACI (Application Configurable Items) capability, and miscellaneious new static and "intelligence" features - the 2.1 additions to WebCGM 2.0. It also incorporates the WebCGM 1.0 test suite. Therefore implementations that pass the WebCGM 2.0 test suite are tested on the WebCGM 1.0 functionality as well (with the exception of a handful of deprecated and obsolete features as documented in the WebCGM Conformance chapter).

As in the 2.0 Test Suite, many of the new tests consist of a number of sub-tests; typically about 5 sub-tests per listed test (one HTML/script file).

Comments on this document should be sent to public-webcgm@w3.org. The archive of public comments is available at http://lists.w3.org/Archives/Public/public-webcgm/.



The WebCGM testsuite is exclusively hosted, maintained and distributed by CGM Open and the WebCGM TC of OASIS. W3C does not have any control over or relationship to the WebCGM testsuite. Publication of this document or the WebCGM 2.1 Specification by W3C indicates no endorsement whatsoever by W3C. The testsuite remains entirely within the responsibility of CGM Open and OASIS. Consequently, W3C declines all responsibility that may arise from the use of the WebCGM testsuite. Neither does W3C make any assertion on intellectual property attached to the WebCGM testsuite. For information on copyright and the applicable patent policy, please look at the site of the OASIS CGM Open WebCGM Technical Committee and the corresponding OASIS Policies on intellectual property rights.

Introduction

This release version of the WebCGM 2.1 Test Suite (WebCGM21TS) covers:

Future releases and further improvements, bug fixes, etc., are anticipated.

The core of the WebCGM 2.0 Conformance Test Suite (WebCGM20TS) is the WebCGM 1.0 Test Suite (WebCGM10TS), comprising about 250 test cases. The WebCGM10TS was developed by Lofton Henderson and NIST (National Institute of Standards and Technology). CGM Open has provided a Web location for free distribution of the WebCGM10TS since its first publication. Copyright of the WebCGM10TS is held by Lofton Henderson. License terms for use and redistribution are free, subject to a no-modification restriction (to preserve the integrity of WebCGM10TS materials). See the "WebCGM10TS copyright & license" document (in the downloadable ZIP archive of the test suite).

About.

Composition. The composition of the WebCGM 2.1 test suite is as follows:

Test versions. The WebCGM 2.1 profile has a conformance rule that the metafile must be identified by the "ProfileEd:2.1" string. A similar rule is present in the WebCGM 2.0 profile ("ProfileEd:2.0"), and the WebCGM 1.0 profile ("ProfileEd:1.0"). Except for this requirement, most valid 1.0 and 2.0 metafiles would be valid 2.1 metafiles. I.e., if their identifer string were changed to 2.1, they would be valid 2.1 metafiles.

In the initial release of the WebCGM21TS, most of the files in the previous editions — WebCGM10TS and WebCGM20TS metafiles — have been left "as is". I.e., their identifiers have not been changed to "ProfileEd:2.1". Exceptions have been made in cases where WebCGM 2.1 has changed the associated conformance requirements in the test. In such cases, the ProfileEd has been changed to 2.1. In other words, the ProfileEd in any test of the WebCGM21TS actually denotes the oldest edition of the WebCGM profile for which the test is valid.

It is planned that a future release of this WebCGM21TS will change all files to contain "ProfileEd:2.1". Please see the Release Notes (in the downloadable ZIP file) for up-to-date information about particular Test Suite releases.

Caveats.

Please check the Release Notes (in the downloadable ZIP file) for any up-to-date information about the following Test Suite caveats.

  1. Some of the dynamic tests (of WebCGM10TS subset) involve HTML as either a source or destination of hyperlinks. In some cases, the HTML text was borrowed from the WebCGM 1.0 specification. Some of these HTML snippets have not yet been updated by the corresponding snippets from WebCGM 2.1. Although the tests are functionally correct, the ultimate goal is to update all of those snippets for clarity and cosmetic reasons.
  2. Some CGMs and PNG reference images still reflect pre-release version numbers, e.g.," 0.9". The tests are functionally correct, and this cosmetic defect may be fixed in a future release.
  3. The Dynamic (hyperlinking) tests (of WebCGM10TS subset) may not look very good if you are running on a small screen, or at less that 1024x768 resolution. (At higher resolutions, there may also be some frame-layout issues).
  4. In a some cases, production of reference images was problematical for WebCGM20TS (as well as WebCGM10TS), due to limited access to high-resolution systems and tools. This may be addressed in a future release. This is not a critical criterion for the dynamic10 tests, in particular, and there is a caveat at the end of each Operator Script.

Installation Instructions

To view WebCGM21TS, all you have to do is unzip the delivery into a local directory. Be sure to pay attention to these details when un-zipping:

After you have successfully unzipped the contents:

  1. open the introPage.html in a browser, or navigate there from this page (see Overview.html in the downloaded ZIP file)
  2. click the link to the dynamic module, the static-graphics module, the 20tests, or the new 21tests
  3. If you choose "Dynamic", this will display a Table of Contents of test cases. Select any one.
  4. If you choose "20tests", this will display a Table of Contents of test cases of the WebCGM20 add-on module (see About). Select any one.

    If you choose "21tests", this will display a Table of Contents of new WebCGM 2.1 test cases. Select any one.

  5. You will need a WebCGM plug-in at this point (selecting tests from the TOCs).
  6. If you select "Static", then you will be taken to a Javascript page (this will not work in older versions of Netscape Navigator — you may have to switch to Internet Explorer or another browser).
  7. You can navigate to any one of the 200+ static tests, by one of several selection categories.
  8. The Operator Script will be displayed, plus a button to display the (raster) reference image. You will have to cause your viewer (plugin, or standalone, or...) to display the CGM.

Test cagories - additional details

Dynamic10 tests

The tests in this category have names like: linking-basicH2C-BE-01. The first bit is the functional category, the second is the specific focus, the third is test type (all of these are BE, Basic Effectivity), the 4th is a sequence (within category): category-focus-BE-nn.. All of the tests are BE tests. They try to provide a complete coverage of V4 functionality at a basic level of detail no drill down or detailed testing (DT).

When you select a test in the TOC, a 4-frame screen will come up.

For information (but not relevant to viewing and using the test suite), the test cases are each driven off of an XML test case description instance, and XSLT stylesheets generate the test harnesses.

There are many files associated with each test case. You don't need to worry much about most of them. But a couple of files might interest you. The test content root file will generally be named "category-focus-BE-nn" with extension .cgm or .html. If the test case has a target file for a link, it will be named something line "category-focus-BE-nn-target", with extension .cgm or .html. All of the files with bits like "-dyn" as a suffix to the name are associated with the harness, and you shouldn't need to worry about them.

Test cases have names like: linking-basicH2C-BE-01. The first bit is the functional category, the second is the specific focus, the third is test type (all of these are BE, Basic Effectivity), the 4th is a sequence (within category): category-focus-BE-nn.. All of the tests are BE tests. They try to provide a complete coverage of V4 functionality at a basic level of detail - no drill down or detailed testing (DT).

When you select a test in the TOC, a 4-frame screen will come up.

For information (but not relevant to viewing and using the test suite), the test cases are each driven off of an XML test case description instance, and XSLT stylesheets generate the test harnesses.

There are many files associated with each test case. You don't need to worry much about most of them. But a couple of files might interest you. The test content root file will generally be named "category-focus-BE-nn" with extension .cgm or .html. If the test case has a target file for a link, it will be named something line "category-focus-BE-nn-target", with extension .cgm or .html. All of the files with bits like "-dyn" as a suffix to the name are associated with the harness, and you shouldn't need to worry about them.

WebCGM 2.0 tests.

The majority of these are DOM and XCF tests, that each start with an HTML page. Typically there is a reference picture (PNG) on one side, a frame for display of the subject source metafile the other side, and an HTML table below, with interactive buttons for triggering DOM calls and/or other subtests.

WebCGM 2.1 tests.

These are mostly tests for the functionality added to WebCGM by the 2.1 edition. Each start with an HTML page. Typically there is a reference picture (PNG) on one side, a frame for display of the subject source metafile the other side, and an HTML table below, with interactive buttons for triggering the various sub-tests.

Download

You can download a ZIP file and install the test suite on a local computer.

View Intro Page. In the future, you will be able to browse the suite online. For now, you must download, install it per the above instructions, and initiate viewing at introPage.html. Either way, if you view the Intro page, it will have links that take you to the various parts of the suite. Please note viewer and browser requirements discussed above.

Feedback Welcome. We welcome specific critiques on individual tests, Your general comments and impressions are welcome as well. Contributions can be made with the contribution form (test-contribution-grant.html) enclosed in the downloadable ZIP archive of the test suite. Please send comments and contributions to the WebCGM TS manager, or info@cgmopen.org.

Questions? Please write to WebCGM TS manager, or info@cgmopen.org.


Lofton Henderson, WebCGM Working Group Chair.

06 August 2009.

Last Updated: $Date: 2009/12/16 20:58:06 $