This documents shows the results of EPUB 3.3 Testing. It corresponds to the EPUB 3.3 specification's category 1 exit criteria, as well as the complete exit criteria for the EPUB 3.3 Reading Systems specification.
This document contains the test results for all tests. There is a separate document which provides a short description for each test; these descriptions are derived from the tests in the tables below.
In the EPUB community, implementors may develop one or more EPUB Reading System rendering engines which are then used in multiple applications across different platforms (ex. iOS, Android, or Web). To accurately reflect this in our tests, we have "variants", which allow the implementors to report results based on both the core engine and the platforms they support using that engine. From a W3C Process point of view, these variants should not be considered independent implementations. We are reporting the results of the different variants for the benefit of implementors and the EPUB community, who may find it beneficial to know how implementations support EPUB features across platforms.
The report tables in sections 3 and 4 reflect this implementation process. shows a view of the reports where reports with identical core engines are consolidated into a single implementation. The test results for a specific test is set to pass if any of the variants has a pass value. The separate shows the full implementation results for each implementation.
lists all the implementations and their variants. The variant will appear after the implementation name, and may include a version number for the software tested and what browser or platform it was tested on.
The report tables also include a separate column (with the heading "Req") providing the conformance level for the feature being tested (i.e., must, should, or may).
The should and may tests are not necessary for the official CR testing of
the specifications. Implementors and the EPUB community may find these results useful, which is why they were gathered.
These tests are currently visible in the tables; to change their visibility, click the
switch visibility button below.
The development of the tests is a community effort (see the list of contributors). Everyone is welcome to contribute tests; please read the separate contribution guidelines if you are interested in doing so.