Test fixtures added.

An example test specification as well as matching test steps are in
place, which will provide a way to test out the documentation features
once YARD is integrated.
Test definition handler.

A handler for test definitions exists such that any methods beginning
with the Gherkin keywords are handled by the process operation of the
handler.
Test transform handler.

A handler for test transforms exists such that any methods beginning
with the keyword Transform are handled by the process operation of the
handler.
Start of code objects support.

Classes for providing code object instances of test definitions and
test transforms have been put in place, both of them deriving from
the base code object implementation of YARD.
Handlers create code objects.

Minimal logic is in place to handle creating an instance of a code
object via a handler. This was the first step on the path to being
able to register code objects with the YARD registry.
Test processor object added.

There is a TestProcessor that is now the parent of both the code
objects for test definitions and test transforms. This was done
since there is clearly a lot of commonality between the two code
objects. This paved the way for creating new instances of the
code objects and registering them.
Lucid namespace provided.

A Lucid namespace has been created to hold the parsed artifacts. The
artifacts that YARD will have to use in order to parse the code-based
structures of a Lucid repository are largely in place from a pure
structural perspective.