Test Suite Overview

From SVG

This page is out of date and is not longer being maintained. Please see https://github.com/w3c/svgwg/wiki/Testing for details on the working group's plans for testing SVG.

This page points to the various versions of the test suites for Scalable Vector Graphics (SVG).


The test suite for SVG 2 is still under development, and a link to the current version will be provided as soon as it's available.

Previous versions of the SVG test suite used a different test framework, and we are now transitioning to the common web-platform-tests framework. All relevant previous tests are being updated to this framework, and all new test will be written to conform with it.

Prior Versions

Welcome to the current releases of the SVG Full and SVG Mobile Test Suites. W3C creates and maintains test suites as part of its Recommendation Track process, to enforcing the high quality of its specifications by ensuring that the wording is clear enough to yield two or more interoperable independent implementations for each feature. The results of these test suites are available in our implementation reports, which indicate how many implementations support each tested feature. Ideally, each feature of SVG will have several supporting browsers/viewers and at least one supporting authoring tool.

A Note On Implementability vs. Conformance Testing

One of the goals of W3C as an standards organization is to promote wide interoperability across devices, platforms, and classes of user agents (such as browsers and content authoring tools). Test suites are an important part of that, but W3C does not certify implementations. Our test suites are necessary, but not sufficient, to test conformance.

Some tests target one very specific feature, while others combine several features in combination. Some particularly complicated features may have many tests, while relatively simple or basic features may have fewer tests. Thus, representations of tested support is skewed toward the more complex features of SVG, and is not an accurate view of overall SVG support, and the SVG Test Suite and corresponding implementation reports are not suitable or intended to show conformance for any given implementation. In other words, W3C tests the specification, not the browsers.

However, these tests can be used by implementors to as part of their own conformance test suites, and consumers can assess the suitability of any given implementation using individual tests for desired features.

Implementation reports show a snapshot in time of implementation support for each tested feature, corresponding to the progress of the specification along the W3C Recommendation Track, and are dated accordingly. The creation of tests, and reporting the results, is an ongoing effort, though, and the SVG WG may update the test suite to provide further clarification on certain features, and to more accurately show how well those features are supported.

Test Development

These tests are created according to the W3C Test Development FAQ in general, and the SVG Test Suite Manual in particular. All tests have been submitted under the Policies for Contribution of Test Cases to W3C, copyright and test suite distribution are governed by the W3C Document License and the W3C Member agreement. This policy both promotes the distribution of a test suite as it was agreed upon within W3C and protects the test suite from unapproved modifications that might harm interoperability.

Any questions or comments about these tests, including bug reports, can be filed with the SVG WG in the manner described on the SVG Feedback Page.

How to Create Tests

Please consult SVG2/Testing_Requirements when making SVG2 tests. Note that the test template has changed compared to SVG 1.1.

Also maybe still useful: New SVG Tests.

SVG 1.1 Second Edition Test Suite: 16 August 2011

The 16 August 2011 release of the SVG 1.1 Second Edition Test Suite includes a total of 445 tests, most with numerous subtests.

Tests are available using a number of different harnesses.

All accepted tests:

All tests regardless of status:

Note: Tests that contain the draft-watermark are under development and may be incorrectly testing a feature.

An archive of the test suite is available here:

Implementation report

There is a implementation report available for SVG 1.1 Second Edition:

SVG 1.2 Tiny Test Suite: 12 September 2008

The September 12 2008 Beta 3 release of the SVG 1.2 Tiny Test Suite includes a total of 495 approved tests. This is a subset of the 578 tests currently in the archive. Note: the revision numbers on the reference images are for internal use only, and may not be in sync with the revision numbers on the test itself; this does not affect the applicability or pass criteria of the tests.

Currently, the entire beta test suite is available in several harness formats as a compressed archive.

There is a list of known issues with the Beta 3 release:

Tests are available with a harness in HTML:

You can also download and archive of this beta release of the testsuite

Implementation Report

The implementation report was created following the SVG Tiny 1.2 test fest was held Sept 29 - Oct 2, 2008 in Ottawa, Canada.

SVG 1.1 First Edition Test Suite: 13 December 2006

The 13 December 2006 release of SVG 1.1 and SVG Mobile Test Suite includes a total of 275 tests, most with numerous subtests.

The same tests are available with a variety of test harnesses, as follows:

Tests in HTML using the <object> element:

Tests in HTML using <embed> element:

Tests in SVG using <image> element:

Download archives of the Testsuite

Implementation Report

There is a implementation report available for SVG 1.1. Note that this is not a comprehensive report, and may not reflect the current state of implementations; since this report was published (in August 2003), there has been substantial implementation by Mozilla Firefox, Opera, and Safari.

Note that this is not a comprehensive report, and documents a moment in time when SVG 1.1 was exiting Candidate Recommendation. It does not reflect the current state of implementations; in the seven years since this report was published, there has been substantial implementation by Mozilla Firefox, Opera, and Safari.