You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "davsclaus (via GitHub)" <gi...@apache.org> on 2026/10/16 19:36:45 UTC
[PR] CAMEL-23688: camel-jbang - Tests for cmd browse and cmd stub [camel]
davsclaus opened a new pull request, #27973:
URL: https://github.com/apache/camel/pull/27973
Eighth batch of [CAMEL-23688](https://issues.apache.org/jira/browse/CAMEL-23688) (test coverage of the CLI commands): the views of `camel cmd browse` (57% line coverage before) and `camel cmd stub` (46%), which only had a test of the request and one of a name that matches nothing.
### Tests
- `CamelBrowseActionViewsTest` (new): the endpoints and their size (`100+` at the limit), `--sort`, `--mask`, the dump of the messages (what the request asks for: the endpoint, `--tail`, `--body-max-chars`), `--only-body`, JSON with the messages, and the errors.
- `CamelStubActionViewsTest` (new): the queues, `--sort`, `--filter`, `--browse` (the latest message first), `--grep` with `--show-headers=false`, JSON, and an unknown `--sort`.
### Bug the tests found
- **`camel cmd browse --endpoint`** with an endpoint that the integration cannot browse, or does not have, printed an empty table and exited with `0`; now not found (`3`), as a name that matches no integration is. The user-visible change is in the 4.24 upgrade guide.
`mvn test` of camel-jbang-core: all tests pass.
_Claude Code on behalf of davsclaus_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01DDRLJAyf8cDXSg8iX785My
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-23688: camel-jbang - Tests for cmd browse and cmd stub [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus merged PR #27973:
URL: https://github.com/apache/camel/pull/27973
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-23688: camel-jbang - Tests for cmd browse and cmd stub [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #27973:
URL: https://github.com/apache/camel/pull/27973#issuecomment-6223893792
<!-- ci-tested-modules -->
:test_tube: **CI tested the following changed modules:**
- `docs`
- `dsl/camel-jbang/camel-jbang-core`
:repeat: **1 test passed only after a retry on JDK 25** (1 retried attempt)
<details><summary>Recovered flaky tests on JDK 25 (1)</summary>
| Module | Test | Failed attempts | First failure |
| --- | --- | --- | --- |
| `dsl/camel-jbang/camel-jbang-plugin-tui` | `LaunchManagerOutcomeTest.startedWhenTheStatusFileSaysSo` | 1 | expected: null but was: LaunchOutcome[ok=false, log=null] |
> :information_source: These tests did **not** fail the build. Surefire retried them and they passed.
> Retries are enabled project-wide by `surefire.rerunFailingTestsCount` in `parent/pom.xml`.
</details>
---
<details><summary>:microscope: Scalpel shadow comparison — Scalpel: 5 of 706 tested, 8 compile-only — current: 5 all tested</summary>
[Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **5 affected modules** (current approach: 5).
**Skip-tests mode would test 5 modules** (2 direct + 5 downstream), **skip tests for 8** (generated code, meta-modules)
<details><summary>Modules Scalpel would test (5)</summary>
- `camel-jbang-mcp` ← downstream of org.apache.camel:camel-jbang-core
- `camel-jbang-plugin-mcp` ← downstream of org.apache.camel:camel-jbang-core
- `camel-jbang-plugin-tui` ← downstream of org.apache.camel:camel-jbang-core
- `camel-jbang-plugin-validate` ← downstream of org.apache.camel:camel-jbang-core
- `camel-launcher-container` ← downstream of org.apache.camel:camel-launcher
</details>
<details><summary>Modules with tests skipped (8)</summary>
- `camel-jbang-it`
- `camel-jbang-main`
- `camel-jbang-plugin-edit`
- `camel-jbang-plugin-generate`
- `camel-jbang-plugin-kubernetes`
- `camel-jbang-plugin-test`
- `camel-launcher`
- `coverage`
</details>
> :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel)
</details>
:warning: **Some tests are disabled on GitHub Actions** (`@DisabledIfSystemProperty(named = "ci.env.name")`) and require manual verification:
- `dsl/camel-jbang/camel-jbang-core`: 2 test(s) disabled on GitHub Actions
:bulb: **Manual integration tests recommended:**
> You modified `dsl/camel-jbang/camel-jbang-core`. The related integration tests in `dsl/camel-jbang/camel-jbang-it` are excluded from CI. Consider running them manually:
> ```
> mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test
> ```
<details><summary>All tested modules (15 modules, 3m 8s total)</summary>
**Total reactor time:** 3m 8s
| Module | Duration | Status |
| --- | --- | --- |
| Camel :: Launcher | 50.0s | SUCCESS |
| Camel :: JBang :: MCP | 42.9s | SUCCESS |
| Camel :: JBang :: Plugin :: Validate | 37.5s | SUCCESS |
| Camel :: JBang :: Plugin :: Testing | 17.3s | SUCCESS |
| Camel :: Docs | 16.8s | SUCCESS |
| Camel :: JBang :: Plugin :: Kubernetes | 13.6s | SUCCESS |
| Camel :: Coverage | 2.0s | SUCCESS |
| Camel :: JBang :: Plugin :: MCP | 1.8s | SUCCESS |
| Camel :: JBang :: Plugin :: Generate | 1.5s | SUCCESS |
| Camel :: JBang :: Plugin :: Edit | 1.5s | SUCCESS |
| Camel :: JBang :: Main | 1.3s | SUCCESS |
| Camel :: JBang :: Integration tests | 0.9s | SUCCESS |
| Camel :: Launcher :: Container | 0.7s | SUCCESS |
| Camel :: JBang :: Core | n/a | |
| Camel :: JBang :: Plugin :: TUI | n/a | |
**Top 20 slowest modules:**
- `Camel :: Launcher` (50.0s)
- `Camel :: JBang :: MCP` (42.9s)
- `Camel :: JBang :: Plugin :: Validate` (37.5s)
- `Camel :: JBang :: Plugin :: Testing` (17.3s)
- `Camel :: Docs` (16.8s)
- `Camel :: JBang :: Plugin :: Kubernetes` (13.6s)
- `Camel :: Coverage` (2.0s)
- `Camel :: JBang :: Plugin :: MCP` (1.8s)
- `Camel :: JBang :: Plugin :: Generate` (1.5s)
- `Camel :: JBang :: Plugin :: Edit` (1.5s)
- `Camel :: JBang :: Main` (1.3s)
- `Camel :: JBang :: Integration tests` (0.9s)
- `Camel :: Launcher :: Container` (0.7s)
</details>
---
:gear: [View full build and test results](https://github.com/apache/camel/actions/runs/38956191682)
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-23688: camel-jbang - Tests for cmd browse and cmd stub [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #27973:
URL: https://github.com/apache/camel/pull/27973#issuecomment-6223271998
:star2: Thank you for your contribution to the Apache Camel project! :star2:
:robot: CI automation will test this PR automatically.
:camel: Apache Camel Committers, please review the following items:
* First-time contributors **require MANUAL approval** for the GitHub Actions to run
* You can use the command `/component-test (camel-)component-name1 (camel-)component-name2..` to request a test from the test bot although they are normally detected and executed by CI.
* You can label PRs using `skip-tests` and `test-dependents` to fine-tune the checks executed by this PR.
* Build and test logs are available in the summary page. **Only** [Apache Camel committers](https://camel.apache.org/community/team/#committers) have access to the summary.
:warning: Be careful when sharing logs. Review their contents before sharing them publicly.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org