gnodet opened a new pull request, #24509:
URL: https://github.com/apache/camel/pull/24509

   ## Summary
   
   _Claude Code on behalf of gnodet_
   
   `MockEndpoint.assertIsSatisfied()` already uses an internal `CountDownLatch` 
that waits up to **10 seconds by default** (see `MockEndpoint.java` line 1997: 
`waitTime = timeout == 0 ? 10000L : timeout`), making Awaitility wrapping 
entirely redundant.
   
   This PR replaces all **58 instances** across **49 test files** in **18 Maven 
modules** with native MockEndpoint timed assertions:
   
   - **For timeouts ≤ 10s**: plain `assertIsSatisfied()` (uses built-in 10s 
default)
   - **For timeouts > 10s on instance calls**: `setResultWaitTime(millis)` + 
`assertIsSatisfied()`
   - **For timeouts > 10s on static calls**: `assertIsSatisfied(context, N, 
TimeUnit.SECONDS)`
   
   Awaitility/Duration/TimeUnit imports are cleaned up where no longer used 
elsewhere in the file.
   
   **Related**: follows the guidance documented in #24496.
   
   ### Affected modules
   
   `camel-core`, `camel-quartz`, `camel-snmp`, `camel-leveldb`, `camel-netty`, 
`camel-file-watch`, `camel-mllp`, `camel-mybatis`, `camel-mina`, 
`camel-mongodb`, `camel-jms`, `camel-sjms`, `camel-kafka`, `camel-ftp`, 
`camel-chatscript`, `camel-zeebe`, `camel-aws2-s3`, `camel-aws2-kinesis`
   
   ## Test plan
   
   - [x] All 49 files compile successfully
   - [x] `core/camel-core` — 18 test classes pass (file, processor, throttle 
tests)
   - [x] `camel-quartz` — 3 tests pass
   - [x] `camel-snmp` — 3 tests pass
   - [x] `camel-leveldb` — 2 tests pass
   - [x] `camel-netty` — 1 test passes
   - [x] `camel-file-watch` — tests pass
   - [x] `camel-mybatis` — tests pass
   - [ ] Integration tests requiring external services (kafka, mongodb, jms, 
ftp, aws, zeebe, chatscript) — need CI
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to