> Christopher Elkins wrote:
> >
> > Hi, all.
> >
> > While implementing OR query support in Criteria, I'm planning to create the
> > beginnings of a JUnit test-case for it. What are people's opinions on the
> > location of the test classes? I see at least two options:
> > (1) src/java/org/apache/turbine/tests
> > (2) src/tests
> >
> > Feel free to suggest other locations and/or naming conventions.
> >
> > Additionally, I see at least two options for organizing the test classes
within
> > the test root directory:
> > (1) place all classes in one directory (which seems like a bad idea)
> > (2) mirror the directory heirarchy of the main source code - for
example,
> > the CriteriaTest class would be located in [test_root]/util/db
> >
> > Thoughts?
>
> FYI, if you do it either of these ways, you can't easily test protected
> or private methods.
True. However, (to state the obvious) the only way we could _ever_ test private
methods is by embedding the test code in the class to be tested; to test
protected methods, the test class would have to extend the class to be tested.
Another disadvantage of the two options above is that we wouldn't be able to
test package-private classes.
I guess it boils down to whether the unit-tests should emphasize white-box or
black-box testing. The options I outlined above implicitly assume that black-box
testing has priority.
> --
>
> Daniel Rall <[EMAIL PROTECTED]>
>
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
