From 144a0b3ec3707d9017beca6e78e564f0d68a3e29 Mon Sep 17 00:00:00 2001
From: John Mark Bell <jmb@netsurf-browser.org>
Date: Mon, 12 Jan 2009 23:17:04 +0000
Subject: Document testdata format

svn path=/trunk/libcss/; revision=6053
---
 test/data/parse/README | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 test/data/parse/README

(limited to 'test')

diff --git a/test/data/parse/README b/test/data/parse/README
new file mode 100644
index 0000000..14edf37
--- /dev/null
+++ b/test/data/parse/README
@@ -0,0 +1,48 @@
+Parser testcases
+================
+
+Format
+------
+
+#data
+<css source data>
+#errors
+<list of expected errors, with line/col offsets> (ignored at present)
+#expected
+<rule list, as below>
+#reset
+
+Format of rule list
+-------------------
+
+  line     ::= rule | bytecode
+  rule     ::= '| ' type ' '+ name
+  name     ::= .+
+  type     ::= [0-9]+
+  bytecode ::= '|  ' ' '* hexnum (' '+ hexnum)*
+  hexnum   ::= '0x' [0-9a-fA-F]+
+
+Type corresponds to css_rule_type. Consult the library sources for the values.
+
+Bytecode may be split over multiple lines for readability. All bytecode is
+associated with the most-recently-declared rule.
+
+Example
+-------
+
+#data
+* { color: #ff0000 }
+#errors
+#expected
+| 1 *
+|   0x0200000f 0xff000000
+#reset
+
+TODO
+----
+
+  + Permit nesting of rules (for nested block support)
+  + There's no way of flagging a pointer in the bytecode (ideally, this will
+    be defined in such a way that we'll be able to validate the data pointed
+    to, too)
+
-- 
cgit v1.2.3