Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig >> mail # dev >> Pig test package structure

Copy link to this message
Pig test package structure

Is there a good reason why almost all pig tests live in org.apache.pig.test
and not in the package of the class they're testing? This approach means
that many methods need to be made public just for testing instead of
package private. It also makes it harder to find tests in a package with
212 classes in it.

What would people feel about changing this standard to put test classes in
the package name of the class you're testing? It would be great to move
classes to new packages, but then there's that whole breaking patches