[
https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Dettinger updated CAMEL-13342:
-----------------------------------
Description:
Off-shoot from CAMEL-11807 to allow building support for users to be able to
write Camel tests using JUnit 5.
Some exploratory preparation work have been stored in [a dedicated
branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY].
A camel-test-junit5 dedicated module has been created in
[CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826].
A camel-test-spring-junit5 dedicated module has been created in
[CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965].
A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037.
Other modules will follow:
camel-testcontainers-spring-junit5 (prototype
[here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10])
Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has
been released or until open discussions in [the junit
team|https://github.com/junit-team/junit5/issues/1558] has converged.
was:
Off-shoot from CAMEL-11807 to allow building support for users to be able to
write Camel tests using JUnit 5.
Some exploratory preparation work have been stored in [a dedicated
branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY].
A camel-test-junit5 dedicated module has been created in
[CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826].
A camel-test-spring-junit5 dedicated module has been created in
[CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965].
A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037.
Other modules will follow:
camel-testcontainers-spring-junit5 (prototype
[here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10])
camel-cdi-test-junit5 ? (prototype
[here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4])
...
Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has
been released or until open discussions in [the junit
team|https://github.com/junit-team/junit5/issues/1558] has converged.
> Introduce JUnit 5 testing support
> ---------------------------------
>
> Key: CAMEL-13342
> URL: https://issues.apache.org/jira/browse/CAMEL-13342
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
> Reporter: Eric Deandrea
> Assignee: Alex Dettinger
> Priority: Major
> Fix For: 3.0.0
>
>
> Off-shoot from CAMEL-11807 to allow building support for users to be able to
> write Camel tests using JUnit 5.
> Some exploratory preparation work have been stored in [a dedicated
> branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY].
>
> A camel-test-junit5 dedicated module has been created in
> [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826].
> A camel-test-spring-junit5 dedicated module has been created in
> [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965].
> A camel-testcontainers-junit5 dedicated module has been created in
> CAMEL-14037.
> Other modules will follow:
> camel-testcontainers-spring-junit5 (prototype
> [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10])
> Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has
> been released or until open discussions in [the junit
> team|https://github.com/junit-team/junit5/issues/1558] has converged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
