<commit_before>[[Testing-Testing]]
= Testing

Testing is a crucial activity in any piece of software development or
integration. Typically Camel Riders use various different
technologies wired together in a variety of
patterns with different
expression languages together with different forms
of Bean Integration and
Dependency Injection so its very easy
for things to go wrong! {icon-frown}. Testing is the crucial weapon to ensure
that things work as you would expect {icon-smile}.

Camel is a Java library so you can easily wire up tests in whatever unit
testing framework you use (JUnit 3.x (deprecated) or 4.x).
However the Camel project has tried to make the testing of Camel as easy
and powerful as possible so we have introduced the following features.

[[Testing-Testingmechanisms]]
== Testing mechanisms

The following mechanisms are supported

[width="100%",cols="1,1m,4",options="header",]
|=======================================================================
|Name |Component |Description
|Camel Test |camel-test |Is a standalone Java
library letting you easily create Camel test cases using a single Java
class for all your configuration and routing without using CDI or Spring for
Dependency Injection which does not
require an in-depth knowledge of CDI or Spring + Spring Test.
Supports JUnit 3.x (deprecated) and JUnit 4.x based tests.

|CDI Testing |camel-test-cdi | Provides a JUnit 4
runner that bootstraps a test environment using CDI so that you don't have
to be familiar with any CDI testing frameworks and can concentrate on the
testing logic of your Camel CDI applications. +
Testing frameworks like http://arquillian.org[Arquillian]
or https://ops4j1.jira.com/wiki/display/PAXEXAM4[PAX Exam], can be used<commit_msg>Polish and cleanup documentation<commit_after>[[Testing-Testing]]
= Testing

Testing is a crucial activity in any piece of software development or
integration. Typically Camel Riders use various different
technologies wired together in a variety of
patterns with different
expression languages together with different forms
of Bean Integration and
Dependency Injection so its very easy
for things to go wrong!. Testing is the crucial weapon to ensure
that things work as you would expect.

Camel is a Java library so you can easily wire up tests in whatever unit
testing framework you use (JUnit 3.x (deprecated) or 4.x).
However the Camel project has tried to make the testing of Camel as easy
and powerful as possible so we have introduced the following features.

[[Testing-Testingmechanisms]]
== Testing mechanisms

The following mechanisms are supported

[width="100%",cols="1,1m,4",options="header",]
|=======================================================================
|Name |Component |Description
|Camel Test |camel-test |Is a standalone Java
library letting you easily create Camel test cases using a single Java
class for all your configuration and routing without using CDI or Spring for
Dependency Injection which does not
require an in-depth knowledge of CDI or Spring + Spring Test.
Supports JUnit 3.x (deprecated) and JUnit 4.x based tests.

|CDI Testing |camel-test-cdi | Provides a JUnit 4
runner that bootstraps a test environment using CDI so that you don't have
to be familiar with any CDI testing frameworks and can concentrate on the
testing logic of your Camel CDI applications. +
Testing frameworks like http://arquillian.org[Arquillian]
or https://ops4j1.jira.com/wiki/display/PAXEXAM4[PAX Exam], can be used
{'fraction_non_alphanumeric': 0.0918748205569911, 'fraction_numerical': 0.008039046798736722, 'mean_word_length': 5.311594202898551, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6195003', 'n_tokens_mistral': 911, 'n_tokens_neox': 859, 'n_words': 470}