- * further. This driver produces TAP version 13. The driver
- * produces a TAP `test point' -- i.e., a result reported as
- * `ok' or `not ok' -- for each input test group. Failure
- * reports and register dumps are produced as diagnostic
- * messages before the final group result. (TAP permits
- * structuerd YAML data after the test-point result, which could
- * be used to report details, but (a) postponing the details
- * until after the report is inconvenient, and (b) there is no
- * standardization for the YAML anyway, so in practice it's no
- * more useful than the unstructured diagnostics.
+ * further. This driver produces TAP version 14, but pretends
+ * to be version 13. The driver produces a TAP `test point' --
+ * i.e., a result reported as `ok' or `not ok' -- for each input
+ * test group. Failure reports and register dumps are produced
+ * as diagnostic messages before the final group result. (TAP
+ * permits structuerd YAML data after the test-point result,
+ * which could be used to report details, but (a) postponing the
+ * details until after the report is inconvenient, and (b) there
+ * is no standardization for the YAML anyway, so in practice
+ * it's no more useful than the unstructured diagnostics.