[
https://issues.apache.org/jira/browse/CAMEL-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18309:
--------------------------------
Summary: camel-debug - Allow to disable timeouts with Camel test (was:
Allow to disable timeouts with Camel test)
> camel-debug - Allow to disable timeouts with Camel test
> -------------------------------------------------------
>
> Key: CAMEL-18309
> URL: https://issues.apache.org/jira/browse/CAMEL-18309
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
> Affects Versions: 3.18.0
> Reporter: Aurélien Pupier
> Priority: Minor
> Fix For: 3.x
>
>
> When debugging a Camel test, it would be convenient to be able to disable
> timeouts.
> Similar feature specific to JUnit test
> [https://junit.org/junit5/docs/current/user-guide/#writing-tests-declarative-timeouts-mode]
> I spotted
> [NotifyBuilder|https://www.javadoc.io/doc/org.apache.camel/camel-core-model/latest/org/apache/camel/builder/NotifyBuilder.html#waitTime(long)]
> which is used in test that has timeouts. Need to lookup if there are other
> ways to have timeouts in test
> I think there would 2 main categories:
> * when Java debugging is used. In this case, maybe can reuse same heurisitic
> than for JUnit
> * when Camel debugging. In this case, the heuristic to detect the debug must
> be different.
> maybe a configuration parameter _camel.test.execution.timeout.mode_ can be
> provided. With potential values {_}enabled{_}, {_}disabled{_},
> _disabled_on_debug._
> The default mode for JUnit is {_}enabled{_}. So I guess we should use it too.
> Maybe worth defaulting to _disabled_on_debug_ when _camel-debug_ is on
> classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
