Changes between Version 10 and Version 11 of NewParrotDeveloperGuide

Timestamp:

01/24/09 01:22:11 (13 years ago)

Author:

tshinnic

Comment:

typos, wrong path

NewParrotDeveloperGuide

@@ -67 +67 @@
 === Test Suite ===
 
-Original Parrot tests where written in Perl. Those Perl tests can be ported to PIR test. This is a good place to earn your feathers and learn more PIR at the same time. [http://www.perlfoundation.org/parrot/index.cgi?convert_existing_tests_to_parrot Converting existing tests to Parrot] covers what you'll need to know about the format of a PIR test. If you're not familiar with the test suite functions, you'll want to review `parrot/runtime/library/Test/More.pir`. The functions section gives a description of the different testing functions, mainly: `plan`, `diag`, `ok`, `nok`, `is`, `is_deeply`, `like`, `isa_ok`, `skip`, `isnt` and `todo`. This is a good time to point out that POD can and usually is embedded in PIR files. So if you're in the root build directory, you can run the following to view the module documentation:
+Original Parrot tests were written in Perl. Those Perl tests can be ported to PIR test. This is a good place to earn your feathers and learn more PIR at the same time. [http://www.perlfoundation.org/parrot/index.cgi?convert_existing_tests_to_parrot Converting existing tests to Parrot] covers what you'll need to know about the format of a PIR test. If you're not familiar with the test suite functions, you'll want to review `parrot/runtime/library/Test/More.pir`. The functions section gives a description of the different testing functions, mainly: `plan`, `diag`, `ok`, `nok`, `is`, `is_deeply`, `like`, `isa_ok`, `skip`, `isnt` and `todo`. This is a good time to point out that POD can and usually is embedded in PIR files. So if you're in the root build directory, you can run the following to view the module documentation:
 
 {{{
-~$ perldoc parrot/runtime/library/Test/More.pir
+~$ perldoc runtime/parrot/library/Test/More.pir
 }}}
 
-You already know that `make test` runs the test suite, but when working on individual tests you'll want to run only the test your concerned with. You can do this using Perl's [http://perldoc.perl.org/prove.html prove] for a Perl test, or either `prove` or Parrot itself for PIR tests.
+You already know that `make test` runs the test suite, but when working on individual tests you'll want to run only the test you're concerned with. You can do this using Perl's [http://perldoc.perl.org/prove.html prove] for a Perl test, or either `prove` or Parrot itself for PIR tests.
 
 {{{