widl: Add a framework for automated testing of IDL files that should succeed or fail to be parsed.

Robert Shearman rob at codeweavers.com
Mon Apr 28 14:37:26 CDT 2008

The expected result is contained within the IDL file being tested, in 
the format of "/* @@ widltest: success|failure message */".
  tools/widl/Makefile.in                            |    2 +
  tools/widl/tests/Makefile.in                      |   29 +++++++++++++
  tools/widl/tests/expr_invalid_array_subscript.idl |   10 +++++
  tools/widl/tests/wide_str_literal.idl             |    3 +
  tools/widl/tests/widltest.sh                      |   46 
  5 files changed, 90 insertions(+), 0 deletions(-)
  create mode 100644 tools/widl/tests/Makefile.in
  create mode 100644 tools/widl/tests/expr_invalid_array_subscript.idl
  create mode 100644 tools/widl/tests/wide_str_literal.idl
  create mode 100755 tools/widl/tests/widltest.sh

This should aid in testing more-obscure parts of the parser that aren't 
necessarily valid when using RPC (and hence don't make sense being put 
in dlls/rpcrt4/tests/server.idl).

I have included two tests examples, one of a failure and one of a 
success. The framework should be expanded in the near future to support 
todos, but I felt it was important to get comments about the general 
idea sooner rather than later.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: e1ad354081656f3b786c7b307468c5e9c5763b20.diff
Type: text/x-patch
Size: 3032 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20080428/bd475201/attachment.bin 

More information about the wine-patches mailing list