The big t/ directory
--------------------

Games::Golf is relatively large and complex.  Internally we go several
layers deep to implement some high level methods.  All method
dependencies of any particular method must be tested first.

The various test files are split in several sections, and are numbered
to ensure they run in the preferred order.  The sections are:

Basic:
 00-09 - Basic stuff

Internals:
 10-19 - Low-level I/O and internals
         (this is where platform-dependant code is tested)
 20-29 - Internal API
         (mainly the Games::Golf::TestSuite::capture() method)

Modules:
 30-39 - Games::Golf::Entry
 40-49 - Games::Golf::TestSuite
 50-59 - Games::Golf

Integration:
 90-99 - Testing the whole framework


The boring details
------------------

Here is the detailed list of the test files:

Basic:
 * 00basic.t     - Basic test: try to load all modules at once.
 * 05os.t        - The Games::Golf::OS helper module

Internals:
 * 10tlimit.t    - Games::Golf::TestSuite methods: new() and limit()
 * 12unixnl.t    - Low-level GGT methods: _capture_unix_nolimit()
 * 12win9xnl.t   - Low-level GGT methods: _capture_win9x_nolimit()
 * 12winntnl.t   - Low-level GGT methods: _capture_winnt_nolimit()
 * 14unix.t      - Low-level GGT methods: _capture_unix()

 * 25capture.t   - GGT internal API methods: capture()

Modules:
 * 30eaccess.t   - Games::Golf::Entry methods: new() and accessors.
 * 31escore.t    - Games::Golf::Entry methods: score()
 * 31etiebreak.t - Games::Golf::Entry methods: tiebreak()
 * 32eok.t       - Games::Golf::Entry methods: ok()
 * 35entry.t     - Games::Golf::Entry: Test the module itself

 * 40taccess.t   - Games::Golf::TestSuite methods: accessors
 * 41tcheck.t    - Games::Golf::TestSuite methods: check() and run()
 * 42taioee.t    - Games::Golf::TestSuite methods: aioee()
 * 42tcompile.t  - Games::Golf::TestSuite methods: compile()
 * 42tsub.t      - Games::Golf::TestSuite methods: makesub(), sub() and ok()
 * 45testsuite.t - Games::Golf::TestSuite: Test the module itself

