On another list, I asked Holger about how to use py.test as a wrapper to 
control non-python tests. He referred me to this example:
self-contained yaml 
example<http://codespeak.net/~hpk/pytest/example/nonpython.html>

This got me going on the issue of collecting and running the tests.

I have a follow-up question about aggregating results from these "foreign 
tests". I am using cxxunit, but the specifics are not important to my question. 
Each non-python test involves multiple asserts, failures and possibly errors. 
These test results could be reported in any of the usual formats (logs, stdout, 
JUnit xml format, custom).

My question is this: is there a good way to track assert pass/fail counts 
correctly in py.test?

One crude idea is to have cxxtest print out its assert attempts, passes and 
failures to a log, parse the log and then deliberately pass and fail a correct 
number of "shadow assertions" in python using the same log messages. Is there a 
more direct way?

Thanks,
Eli

_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev

Reply via email to