camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-6029) Add test support classes for unit testing components
Date Tue, 28 Feb 2017 13:59:45 GMT


Claus Ibsen resolved CAMEL-6029.
    Resolution: Won't Fix

> Add test support classes for unit testing components
> ----------------------------------------------------
>                 Key: CAMEL-6029
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-test
>    Affects Versions: 2.11.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>             Fix For: 3.0.0
> (see the [3.0 roadmap|]
> No matter what choices and changes we make in the core, many tests in components will
start failing. That is because virtually all unit tests in components test much more than
the component itself, by setting up routes, etc. A simple thing would be do create something
like xyzTestSupport (where xyz in {"Component", "Configuration", "Endpoint", "Producer", "Consumer",
"Language", etc... }), that test a respective area without setting up routes and possibly
use a minimal CamelContext (w/o component discover and/or other features). Moving component
unit tests to such a framework is not complicated, a bit tedious, but hopefully we'll benefit
(yet again) from community contributions and gain new committers in the process. This is probably
the first thing that should be done that will allow us to be more productive with the other
improvements. It can also be done in 2.x and won't require any incompatible changes.

This message was sent by Atlassian JIRA

View raw message