Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of foamdino@gmail.com designates
 209.85.218.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=P+vpraxdlW/OpBKqywisXHYgDj512KcpNL6qk2v8jdKw2D09DxTYiiW9/eewMJa51b
         J1kIUSitqwnzUDP0Makmvks0KnOse6h3vPb+q3KIxQzbRbtW+mIKtLEkYWSBocVSpyBX
         bJTn8/LHwcd5WYanW9nGlAA+ENmy0Q5RPfGGs=
MIME-Version: 1.0
Date: Sat, 6 Feb 2010 16:09:14 +0000
Message-ID: <ab8e556c1002060809h656b369ep757c5e588e84d026@mail.gmail.com>
Subject: Integration testing a route before production
From: Kevin Jackson <foamdino@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have a route configured in Spring and I would like to integration
test (from file endpoint with production data to persistence in test
db)

For example:

<camel:route id="integration-test">
  <camel:from ref="file-consumer"/>
  <camel:split streaming="true">
    <camel:tokenize token="\n"/>
    <camel:bean ref="Unmarshaller" method="unmarshall"/>
    <camel:bean ref="Transformer" method="transform"/>
    <camel:to uri="mock:result"/>
  </camel:split>
</camel:route>

Now I want to run this route with production data and ensure that the
sample of data I used in my unit tests is representative and that the
production data doesn't cause my pojos to break in any weird ways.
I'm also interested in seeing how much ram this single route will
consume with realistic data before I add it to the live routes.

# How do I trigger this route to run (in the context of an @Test
decorated method)?
# How do I make any meaningful assertions against the mock:result?

Essentially I want to 'assertNoExceptions' and assertTrue(memoryUsed <
80Mb) (or any other arbitrary value.  If I wire up the db layer I can
assert against the data in the tables, but that's a data centric
approach and I think what I'm after is not easily defined by data.

For example I can prove by induction that if the code works for 1
valid input dataset then it will work for n valid input datasets, so
I'm leaning more towards testing intangibles (performance
[time|space], robustness of handling real workloads/data etc).

Sorry I can't really explain why I feel I need to do this, just that I
think it's necessary in this one particular case - does anyone have
any suggestions for how to at least start up the route in a testing
context?

Thanks,
Kev