Browse files

Mention the make targets 'languages-test' and 'languages-smoke'

in tests.pod.

git-svn-id: d31e2699-5ff4-0310-a27c-f18f2fbe73fe
  • Loading branch information...
1 parent f64c6aa commit c8ca9f07dfc673a9cb6b4ea46c5f5ada8671a9b1 @bschmalhofer bschmalhofer committed Dec 12, 2005
Showing with 6 additions and 0 deletions.
  1. +6 −0 docs/tests.pod
@@ -20,6 +20,9 @@ realclean> and recompile parrot before complaining.
If your architecture supports JIT, you can test parrot JIT engine using C<make
testj>. It works just like C<make test>, but uses the JIT engine when possible.
+C<make languages-test> runs the test suite for most language implementations
+in the languages directory.
=head2 Submitting smoke test results
Parrot has a status page with smoke test results
@@ -32,6 +35,9 @@ smoke server.
It is also possible to run a smoke test on JIT. For that, try running
C<env PARROT_ARGS=-j make smoke>.
+C<make languages-smoke> does smoke testing for most language implementations
+in the languages directory.
=head1 How to write a test
New tests should be added to F<*.t> files. These test files can be found in the

0 comments on commit c8ca9f0

Please sign in to comment.