Results of MiniApp Testing.
This document contains the test results for all tests. There is a separate document giving a short description for each tests; these descriptions are linked from the the tests in the tables below.
Some implementations may come in different "variants": though they have identical MiniApp engines, their behaviors may slightly diverge in different environments (typically iOS, Android, or Web) and, therefore, they are reported separately from one another. From the W3C Process point of view, these variants should not considered to be independent implementations and, therefore, they should be considered as one implementation as far as the formal Candidate Recommendation report is concerned. On the other hand, implementors may see a value in keeping those implementation results separated.
The report tables below reflect this duality. shows a view of the reports where reports with identical core engines, albeit in different variants,
are displayed as if it was a single implementation. The test results for a specific test is set to true if any of the variants has a true value. On the other hand, the separate keeps all the variants separate, showing the full implementation results.
lists all the implementations with the variant in parenthesis, if applicable.
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).
Strictly speaking, the should and may tests are not necessary for the official CR testing of
the specifications. These tests are currently in the tables below; 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.