cross-binding test suite

[John (J5) Palmieri]

I can't look at the tests right now because my box is hosed from forcing
a dbus install with new sonames but I wanted to say two things.  

First:

It is awesome that you want ahead and started this work.

Second:

If you haven't already can you add API for checking if a test is
expected to pass. i.e. I may want to still run tests on incomplete
bindings so as they get complete it would be nice if the test just threw
out warnings for the incomplete bits.  It could also throw out a "This
test is marked incomplete but all tests passed, perhaps it should be
marked as complete" message. 

On Tue, 2006-07-18 at 18:38 +0100, Matthew Johnson wrote:
> I have started speccing and writing a cross-binding test suite. The idea
> is that each binding will implement a set of interfaces and provide a
> client to try and break bindings which implement them badly. So, for
> example you might have a method int sum(int[]) which returns the sum of
> all the values in the array and you might try calling it with an empty
> array to make sure the binding you are calling can handle empty arrays.
> Each client will then be tested against each server.
> 
> My proposed interfaces can be found at
> http://mjj29.matthew.ath.cx/test-introspect.html,
> http://mjj29.matthew.ath.cx/test-introspect.xml
> 
> A screenshot of the test output currently:
> http://mjj29.matthew.ath.cx/Screenshot.png
> 
> the README and Makefile that runs it all:
> 
> http://mjj29.matthew.ath.cx/README
> http://mjj29.matthew.ath.cx/Makefile
> 
> Comments, particularly suggestion on things which might not be testable
> with those interfaces, welcome
> 
> Matt

-- 
John (J5) Palmieri <johnp at redhat.com>