On 1/30/06, Ed Summers <[EMAIL PROTECTED]> wrote: > You typically want to test how a user will want to use your library. > You don't want to write tests for internal stuff. If there are a > sequence of interpendent events that need to be tested I tend to > bundle them in an individual test method.
That makes sense. So here's the classes and test methods I'm thinking of as a start then (this for Ruby,but it's close to Python): Reference ======== new author_names to_s (could test output against test input data) ReferenceList =========== new (load data based on list of citations) add to_s CitationStyle ========== new (load external CSL file and create object) info (print metadata) I'm still not sure about the citations per se. Would that be a good start? After playing with this a bit, I realize I was doing this testing informally, so it's nice to be shown the light! Bruce --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
