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

   # Description
   
   Adds 13 new test classes covering the `process/` package commands in 
`camel-jbang-core` that previously had no unit test coverage:
   
   - `CamelContextTopTest` — memory, thread, throughput, and load fields; 
sort-by-mem ordering
   - `CamelCountTest` — totals, `--total`, `--fail`, combined flags, JSON output
   - `CamelProcessorStatusTest` — processor row display, mean filter 
(exclude/include), JSON output
   - `CamelProcessorTopTest` — sort-by-mean descending with both stream 
orderings
   - `CamelRouteGroupStatusTest` — group display, running filter, mean filter, 
JSON output
   - `CamelRouteGroupTopTest` — sort-by-mean descending with both stream 
orderings
   - `CamelRouteTopTest` — route row display, sort-by-mean descending with both 
stream orderings
   - `DirtyTest` — empty dir early return, orphan detection, running-process 
exclusion, `--clean` deletion
   - `ListGroovyTest` — Groovy compiler stats display, missing section 
handling, JSON output
   - `ListKafkaTest` — Kafka consumer row display, missing section handling, 
JSON output
   - `ListPlatformHttpTest` — endpoint display, management endpoint filtering, 
`--all` flag, JSON output
   - `RestartProcessTest` — early-exit guards for no-match and multiple-match; 
successful re-launch path left as TODO pending `ProcessBuilder` mock support
   - `StopProcessTest` — PID file deletion, `--kill` path via 
`ProcessHandle.destroyForcibly()`, no-match no-op
   
   Also updates `ListProcessTest.testSortByName` (from a prior PR) to verify 
sort ordering is insertion-order independent.
   
   All sort-order tests use distinct PIDs per process, with the same context 
name to trigger the mean tiebreaker, and assert the expected ordering under 
both stream orderings. The `thenAnswer` lambda creates a fresh `Stream.of(...)` 
per invocation to handle commands that call `ProcessHandle.allProcesses()` more 
than once.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   ---
   _Claude Code on behalf of Adriano Machado_


-- 
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