Pharo dev's, I'm lurking around the Pharo project for a while now. As I wanted to get some hands-on experience with Pharo I thought it was a good idea to fix an easy bug and see how it goes. The wiki page on how to contribute, and the two screen casts are a great help for newbies like me. Nevertheless, I was wondering if there was an important aspect missing from these instructions: what about tests? I know there is a hudson server running the tests regularly, but I wonder if many people are paying attention to it. Shouldn't there be some instruction on how to add tests for new functionally (or even for a bugfix, if tests weren't already there), and then some instructions on how to run all (or some subset of) the tests to get confidence you didn't broke anything with your changes?
How do you, experienced Pharo contributors, go about this? Do you guys run these tests before every check-in? Are there many tests to run? Are there some guidelines to writing tests when contributing to Pharo? Thx, Linus
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
