We're tracking the RPerl project using Trello, there's a basic check-list on a card named "Test Suite" on this board:

https://trello.com/b/hQCPeg1d/austin-pm-rperl-development

The in-process test is 05_type_hash.t, which is almost done and is modeled after the working 04_type_array.t. You can see the test file at Github here:

https://github.com/wbraswell/rperl/blob/master/t/05_type_hash.t

After the hash type test is done, then comes the OO inheritance test, the RPerl system functionality for which is already in place, and the basic testing code for which is already largely written in different places around the RPerl codebase.

After the OO inheritance test comes the hand-compiled sorting test, and that's where my RPerl system functionality ends. I'm in the process of choosing a Perl 5 parser now, then comes the automated compiling process.

Wanna help with some test writing? :)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.