You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jan Hallonsten (JIRA)" <ji...@apache.org> on 2019/05/07 11:58:02 UTC
[jira] [Created] (CAMEL-13491)
CamelTestSupport.isCreateCamelContextPerClass no longer works for junit4
tests
Jan Hallonsten created CAMEL-13491:
--------------------------------------
Summary: CamelTestSupport.isCreateCamelContextPerClass no longer works for junit4 tests
Key: CAMEL-13491
URL: https://issues.apache.org/jira/browse/CAMEL-13491
Project: Camel
Issue Type: Bug
Components: camel-test
Affects Versions: 2.23.0
Reporter: Jan Hallonsten
With the changes in
org.apache.camel.test.junit4.CamelTestSupport done during the work on https://issues.apache.org/jira/browse/CAMEL-12534 the camel context is now recreated for every test regardless of the return value from
isCreateCamelContextPerClass()
. Since junit4 creates a new instance of the class for every test the variable tests will be recreated and initialized to 0 for every test.
This condition in tearDown will always be true
{code:java}
// code placeholder
if (tests.compareAndSet(v, v - 1)) {
if (v == 1) {
{code}
which stops the camel context after every test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)