Browse files

Patch from Simon Glover <>:

 1. There are tests in t/pmc as well as t/op now.
 2. Adds a comment about Parrot::Test

git-svn-id: d31e2699-5ff4-0310-a27c-f18f2fbe73fe
  • Loading branch information...
1 parent 4ff0236 commit 553e254a9730e1f23c2609bbaf248246716722af Nicholas Clark committed Mar 19, 2002
Showing with 10 additions and 2 deletions.
  1. +10 −2 docs/tests.pod
@@ -8,9 +8,17 @@ into a new test suite.
=head2 How to write a test
-First, find an appropriate file in C<t/op/*.t>, or create a new one.
+First, find an appropriate file in F<t/op/*.t> (for basic ops) or
+F<t/pmc/*.t> (for anything to do with PMCs). If there isn't an
+appropriate file, create one.
-Add a test by:
+Near the top of each file, you'll see a line like:
+ use Parrot::Test tests => 8;
+This sets up the test harness used to assemble and run the tests,
+and lets it know how many tests you plan to run. New tests should be
+added by:
incrementing the number of planned tests.
putting some code in like this:

0 comments on commit 553e254

Please sign in to comment.