I want to see a document that says how Parrot implementers should write tests for the features they implement. Does *anyone* understand how to do this? If so, could you please step forward and write such a document and become a hero.
I imagine a test writing HOW-TO would cover: * structure of test directories * structure of a test file * walk through some simple tests highlighting different things * advanced stuff Advice on different testing approaches (black box, edges, etc.) can wait for later. For now, assume people know they want to test, and know what they want to test, just tell them how to write those test cases. Thanks, Nat
