Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 64.233.184.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=jBg0CBE2RPiL6fEtFEQGVfeYwAO1adECRwPu+qlJ7Mh/41AT8w22XFlSLwXqHRUcKJ
         oW689BR3AIS9hMcFQNcCDfNp9ab2pFQI7PSz4kx8gRtdWJdc/84Q8l1dItElpwEYfFeH
         wh5qBkOoowr6phbd7tyVLMBKwYtyuKA7196fc=
Message-ID: <ec6e67fd0809081215u6f0b6240w9d8ab5c6e6d9f8e4@mail.gmail.com>
Date: Mon, 8 Sep 2008 20:15:00 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Re: A real camel-test component for Camel 2.0
In-Reply-To: <48C38469.9030902@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4C1FB9C00D24A140906239533638C4D20537039F@EXVS04.exserver.dk>
	 <48C38469.9030902@gmail.com>

2008/9/7 Willem Jiang <willem.jiang@gmail.com>:
> Hi Claus,
>
> +1 for creating a real camel-test component for Camel 2.0.
>
> If we create a real camel-test component with current Camel modules layout,
>  it will introduce the cycle dependency into the camel-core
> camel-test <--> camel-core
> Maybe we could take out the camel-api for the camel-core to resolve this
> cycle dependency.
> camel-api <-- camel-test <-- camel-core
>
> And there are lots of test cases in the org.apache.camel.spring.processor
> package of the camel-spring-test.jar which extents the test classes in the
> camel-core-test.jar, it is a challenge for us to support this kind of code
> reuseability  in the new camel-test component.

Yeah - to do a kinda regression test, I started deriving the spring
tests from the core tests but using spring rather than the Java DSL -
though I do find all that code a tad smelly :)

Apart from those tests, the camel-spring module should ideally just
use the spring-test stuff; so it doesn't really need any code from
camel-core-test or anything.

If we did introduce a camel-test library, we'd not have to use it in
camel-core or camel-spring I don't think; we could always move tests
outside those 2 modules. Plus there's nothing stopping us having
separate modules to test various things in the build.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com