chore: add comprehensive test coverage for camel-jbang-plugin-tui

[gnodet]

Summary

Claude Code on behalf of forgebot

Adds comprehensive test coverage for the camel-jbang-plugin-tui module, which previously had zero tests.

231 total tests across 12 test files covering:

Unit Tests (172 tests, 8 files)

• MonitorContextTest — formatting helpers (formatSinceLast, formatLoad, formatMemory, formatBytes, buildBar), style logic (topTimeStyle, topDeltaStyle), string comparison
• IntegrationInfoTest — integration info lookup (findSelected, findByPid), match logic
• HealthCheckInfoTest — health check comparisons, sorting, state validation
• RouteInfoTest — route info comparisons, sorting
• ProcessorInfoTest — processor info comparisons, sorting, level indentation
• ErrorInfoTest — error info comparisons, sorting, exception type shortening
• EndpointInfoTest — endpoint info comparisons, sorting, direction logic
• ShellPanelTest — JSON parsing helpers (removeJsonEscaping, toFlatJson), color assignment (getColor)

Higher-Level Rendering Tests (59 tests, 4 files)

These tests render TUI tabs into a virtual terminal buffer using Frame.forTesting(Buffer) and inspect the rendered output — verifying text content, colors, styles, and layout:

• HealthTabRenderTest (13 tests) — health check table rendering with UP (GREEN) / DOWN (RED) status colors, empty state placeholder, header columns, border title, readiness/liveness kind column, DOWN-only filter toggle, footer hints, sort cycle
• RoutesTabRenderTest (17 tests) — route table headers, route ID (CYAN) and FROM display, Started (GREEN) / Stopped (RED) colors, failed count RED highlighting, processors section, no-selection prompt, top mode toggle with timing headers, sort column in title, coverage/throughput display
• ErrorsTabRenderTest (15 tests) — error table headers, exchange ID display, short exception name (strips package prefix), route ID CYAN color, handled=true (GREEN) / handled=false (RED) colors, multiple errors, empty placeholder, error count in title, sort cycle, handled filter cycle, footer hints
• MonitorContextRenderTest (14 tests) — renderNoSelection prompt text and DIM style, hint()/hintLast() span generation with YELLOW BOLD keys, rightCell right-alignment, centerCell centering, sortLabel ▼/▲ indicators, sortStyle YELLOW+BOLD for active column

Source Changes

• ShellPanel.java — 3 methods widened from private to package-private (removeJsonEscaping, toFlatJson, getColor) to enable testing

Test plan

• All 231 tests pass locally (mvn test -pl dsl/camel-jbang/camel-jbang-plugin-tui)
• Rendering tests use Frame.forTesting(Buffer) to render tabs into virtual terminal buffers
• Tests verify text content, foreground colors (GREEN, RED, CYAN, YELLOW), style modifiers (BOLD, DIM), and layout
• Tests cover key interactions (sort cycling, filter toggles, mode switches)
• CI build passes

🤖 Generated with Claude Code

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 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 have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• dsl/camel-jbang/camel-jbang-plugin-tui

All tested modules (2 modules)

• Camel :: JBang :: Plugin :: TUI
• Camel :: Launcher :: Container

---

⚙️ View full build and test results

[davsclaus]

Good work adding comprehensive test coverage for the camel-jbang-plugin-tui module — 231 tests across 12 files covering unit tests, rendering tests, and key interaction tests is a solid foundation.

The visibility widening of three ShellPanel methods from private to package-private is a reasonable trade-off for testability, and since this is not a public API class, there's no API impact.

Minor observation: several render test classes reference HealthTabRenderTest.bufferToString() as a shared utility — if more tests are added later, extracting that into a dedicated test helper class would be cleaner.

CI is green, no rule violations found.

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.