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
On Wed, 7 Nov 2001, Nathan Torkington wrote:
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 thought
At 10:38 PM 11/7/2001 +, Alex Gough wrote:
[0] Someone mentioned something about this confusing the line endings
in win32, which will cause erroneous test failures, I might look at this
as well.
*Please* do--it seems to confuse the test harness to no end on CygWin.
