Date: January 27, 2001
The SVG working group has finished building the entire test set of the Basic Effectivity (BE) level of an SVG conformance test suite. This is the second publication of BE tests. The first was a partial release of 70 tests in June, 2000. This release contains 127 BE tests, which span the functionality of the SVG specification.
The entire test suite release is contained in the zip file, rel-20010127.zip. Unzipping this will result in:
#3, #4, #5 and #6 provide linked navigation pages for viewing the test suite.
Please check the SVG web pages at http://www.w3.org/Graphics/SVG for further information, including an implementation matrix covering all of the test cases in this suite.
Unzipping harness-html-20010127.zip will result in:
H2: 127 HTML navigation pages named identically to the test cases;
H3: files for making #H2:
Unzipping harness-svg-20010127.zip will result in:
S2: 127 SVG navigation pages named identically to the test cases, except with a "-nav" suffix to the test case name;
S3: files for making #S2:
Unzipping harness-ps-20010127.zip will result in:
PS2: 127 HTML navigation pages named identically to the test cases, except with a "-ps" suffix to the test case name these contain the frameset for this harness type);
PS3: 127 HTML navigation pages named identically to the test cases, except with a "-ps-top" suffix to the test case name;
PS4: 127 HTML navigation pages named identically to the test cases, except with a "-ps-bottom" suffix to the test case name;
PS5: files for making #PS2, #PS3 and #PS4:
Unzipping harness-svgcmp-20010127.zip will result in:
SC2: 127 SVG navigation pages named identically to the test cases, except with a "-cmpnav" suffix to the test case name;
SC3: files for making #SC2:
- CreateSVGharnessCompare.xslt, generateNames.xslt, navigationBar-svgcmp.xslt
- make-all-svgcmp.bat, make-1-svgcmp.bat
This method is one of two possible methods to be used if your SVG viewer is not a browser plugin.
If the SVG viewer supports this functionality, you should be able to navigate the suite in two windows side by side, with the reference image and description in one, and the rendered SVG content in the other.
If the viewer does not yet fully support the 'image' element, as is the case with some current viewers, then for each test case:
If the SVG viewer fully supports the 'image' element, as is the case with some current viewers, then this alternative to the above two steps may be of interest. Instead of step #2, direct your SVG viewer to toc-svcmp.svg. This is a table of contents written in SVG, linked identically to all of the other navigation harness versions. It wil present the SVG rendering and the PNG reference image side-by-side. It will not display the Operator Script information. (If you want to see that, you would have to simultaneously do something like #1 above.)
This method may be used if your SVG viewer is a browser plugin.
View the file toc-ps.html in a browser. You will see the chapter names of the SVG spec (20001102 draft), each linked to the first test of each chapter.
When you view a test, you will see the PNG reference image on the left and the SVG image on the right (SVG-enabled browsers only). At the bottom, there is a navigation bar and the Operator Script for the test -- description of the test purpose and intended results.
Note. Your display should be operating with addressability of at least 1024x768 if you use this viewing method.
The navigation harness sets of H2, S2 and PS2-PS4 above are generated with the tools supplied in H3, S3 and PS5 respectively. These tools are included on "user beware" basis, and are not to be considered a supported part of this test suite release.
The key component are the stylesheets:
If one uses an XSLT processor to apply these to the XML description file for a test case, the result is a set of HTML navigation pages (with operator script text included in some) and an SVG navigation page. The batch files (make-all-html.bat, make-all-svg.bat and make-all-ps.bat) use the XT tool (of James Clark) to generate the entire set of HTML and SVG navigation pages.
Comments are welcome, and should be directed to: email@example.com.