Hi,
I've been making trivial Javadoc comment annotations to the above class
locally with the eventual aim of resolving GORA-75 as currently the class
is a monster with no real sense of navigation for new guys trying to get to
grips with our modularized testing structure and how this class fits in to
it.
With regards to the above class... at a real abstract level, we have three
test topics, we have employee records, tokendatum records and webpage
records, which all have various characteristics about them which present us
with various storage hurdles. Up to this stage is fine.
DataStoreTestUtil provides everything necessary for the convenience tests
in {@link DataStoreTestBase} to execute cleanly. The tests begin in a
fairly trivial fashion getting progressively more complex as we begin
testing some more advanced configuration and storage transactions and
subsequently more advanced features within the Gora API. In addition to
this class, the first place to look for API functionality is at the
examples directories under various Gora modules. Although we have not got
bundles of examples, it is clear that this is where they will be kept.
My reason for opening GORA-75 was that I got the perception this class was
a bit of a rogue, that it could be more clearly annotated and that
subsequently it was easier for people to understand if they were looking in
from an outside perspective.
To satisfy the above, does every @Test need to be annotated? The names are
fairly straightforward (I think), but this is only because I have been
working with them and know the code.
Thanks
--
*Lewis*
