path: root/tests/py/inet/rt.t.json.output
Commit message (Collapse)AuthorAgeFilesLines
* JSON: Make match op mandatory, introduce 'in' operatorPhil Sutter2018-08-301-0/+2
| | | | | | | | This special operator is required for cases where missing operator does not lead to same results as equal operator, i.e. with bitmasks on RHS. Signed-off-by: Phil Sutter <> Signed-off-by: Pablo Neira Ayuso <>
* JSON: Make meta statement/expression extensiblePhil Sutter2018-08-301-1/+1
| | | | | | | | | | Lessons learned from fwd statement: We must not assume a given statement/expression may not receive further properties in the future. Therefore make meta value an object with a property "key" instead of just a string containing the key name. Signed-off-by: Phil Sutter <> Signed-off-by: Pablo Neira Ayuso <>
* tests/py: Support testing JSON input and output as wellPhil Sutter2018-05-111-0/+23
This extends by optional JSON testing capabilities, activated via '-j'/'--enable-json' parameter). JSON testing happens for all rules which are supposed to work: After a rule has been added and the existing tests (payload, ruleset listing output) have been performed, basically the same test is done again using a recorded JSON equivalent and (if necessary) a recorded listing output. The code tries to ease new test case creation overhead by auto-generating JSON equivalent input via listing the (non-JSON) rule in JSON format. Also, differing netlink debug and listing output are stored in *.got files to assist in analyzing/fixing failing test cases. Signed-off-by: Phil Sutter <> Signed-off-by: Pablo Neira Ayuso <>