score_config_management#

Step 5 — Component-test plan#

Note

The Reference Integration does not yet have a component-test stage (see Step 5 — Add component tests). This page documents the plan for score_config_management so the module is ready to be wired in as soon as the mechanism exists.

Scope#

The plan covers the config_daemon component only. config_provider is a client-side library with no standalone runnable binary today; it is out of scope until a dedicated test harness exists for it.

Component under test#

config_daemon — the service that owns and exposes parameter-set data over its public mw::com service interface (score/config_management/config_daemon/code/services/internal_config_provider_service.h), consumed by config_provider clients.

Reference application#

Reuse the config_daemon binary and configuration already packaged for the Step 4 showcase (showcases/standalone/config_management.score.json / @score_config_management//score/config_management/config_daemon/code:config_daemon). No new binary needs to be built for the component test; it drives the same reference application already validated to run.

Planned test approach#

Once the component-test framework is introduced:

  1. Start the reference config_daemon application with its existing showcase configuration (etc/mw_com_config.json).

  2. Drive it as a black box through its public InternalConfigProvider mw::com service interface only — no internal/implementation-detail access.

  3. Assert parameter-set retrieval behavior (successful reads, missing/invalid parameter handling, service availability) against the component’s documented interface specification.

  4. Run independently of other modules and of full integration images, per the Step 5 definition of component-level verification.

Status#

Documented plan only — not yet executable. No component-test stage exists in the Reference Integration CI yet; this page will be updated with the actual wiring once Step 5 tooling lands.