On Jan 29, 2006, at 9:52 PM, pt wrote:
I agree that test-driven development will help a lot here.
One starting point would be tests that show you can load data into
some object from the RDF serialization suggested by Bruce then re-
serialize it back out. Trivial to implement at first, but needs to
be there as more code gets built.
Bruce, you certainly have the skills to write unit tests that show
how the objects should behave, and hope that others can help fill
in the code. Ed - do you have test frameworks in mind for Python /
Ruby? (I know there are a couple of options in Python - I've used
py.test but not others)
I've used a few different ones, but since I'm in ruby, python and
java pretty frequently I've found myself using unittest, Test::Unit
and junit since they all follow the same xunit pattern. py.test might
be the simplest way to move forward though. I saw Ian Bicking talk
[1] about py.test at a local python meeting and was pretty impressed
with its simplicity.
I'm psyched you agree pt :-) Defining a set of tests that illustrate
how to use the API might be a good way for us to visualize how the
library could be used, and for us to measure our success as the
library gets fleshed out.
//Ed
[1] http://ianbicking.org/docs/pytest-presentation/pytest-slides.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
