Initial prototype for generating pojo classes on the fly to aid testing
multiple combinations
starting to work on creating a test that covers as many possible
interactions of features as possible
Experiment with a few different approaches to data-driven testing 
(using TestNG).
ignore detrius
While it makes sense to provide the type via a data provider, providing
individual values feels like overkill - we end up with too many small
tests. This would only get worse as we add more axes to our test cases.
Better to have this test pass than fail...
Run both TestNG and Junit tests
Rather than having separate tests for arrays and non-arrays, let arrays
be another type.
Test arrays stored in Object fields, both with and without
@CanBeArray