Discrete testing of all Operations, pipe assemblies, and
applications is a must. The
cascading.CascadingTestCase provides a number of
static helper methods.
When testing custom Operations, use the
When testing Flows, use the
validateLength() methods. There are quite a few
of them, and collectively they offer great flexibility. All of them read
the sink tap, validate that it is the correct length and has the correct
Tuple size, and check to see whether the values match a given regular
As of Cascading 2, it is possible to write tests that are
independent of the underlying platform. Any unit test should subclass
cascading.PlatformTestCase located in the
cascading-platform-x.y.z-tests.jar jar file. Any
platform to be tested against should be added to the
CLASSPATH as well.
will search the
CLASSPATH for all available platforms and
run each test on the subclass against each platform found.
See the Cascading platform unit tests for examples.
For Maven users, be sure to add the
to any dependencies. Note that the
project has no main code, but does have only tests, so it must be
retrieved via the
Copyright © 2007-2012 Concurrent, Inc. All Rights Reserved.