Repository navigation
docs: add Unit Test work product for mw::log backend - #376
Draft
Y-Vaishnavi wants to merge 1 commit into
Draft
Y-Vaishnavi wants to merge 1 commit into
Y-Vaishnavi wants to merge 1 commit into
Conversation
Adds a formal document:: page realizing wp__verification_sw_unit_test for the log_backend component, linking the existing gTest unit test suites under score/mw/log/ to the work product. Replaces the placeholder '<Link to WP>' entry in the module safety plan with a reference to the new doc. Fixes eclipse-score#231
Y-Vaishnavi
requested a deployment
to
workflow-approval
October 26, 2026 07:13 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
Y-Vaishnavi
requested a deployment
to
workflow-approval
October 26, 2026 07:13 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Y-Vaishnavi
requested a deployment
to
workflow-approval
October 26, 2026 07:13 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Y-Vaishnavi
requested a deployment
to
workflow-approval
October 26, 2026 07:13 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Contributor
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
rmaddikery
reviewed
Oct 26, 2026
| :need:`gd_guidl__verification_guide`, and are integrated into the CI build so | ||
| that they run on every change. | ||
|
|
||
| Unit Test Suites |
Contributor
There was a problem hiding this comment.
It is not ideal to list every test target here again. I would suggest to provide a landing page that navigates to all in one link. Otherwise its a maintenance effort!
rmaddikery
requested changes
Oct 26, 2026
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Completes the Unit Test work product (
wp__verification_sw_unit_test) for thelog_backendcomponent by adding a formal.. document::page that:realizes: wp__verification_sw_unit_test.Why
The module safety plan's work-product table had a placeholder
<Link to WP>forwp__verification_sw_unit_test. The gTest unit tests already exist underscore/mw/log/(detail/common, syslog, slog, data_router, file_recorder, wait_free_producer_queue, signal_handling, backend, legacy_non_verbose_api, test), but there was no formal documentation page tying them to the work product.Changes
docs/components/mw_log/detailed_design/unit_test.rst: newdocument::page (doc__mw_log_backend_unit_test) describing and linking all unit test suite locations for the component.detailed_designtoctree.<Link to WP>placeholder indocs/module/safety_mgt/module_safety_plan.rstwith a reference to the new doc.Validation
bazel run //:docs— build succeeds.bazel run //:docs_check— passes with only 4 pre-existing, unrelated warnings (architecturefulfilslinkage in a different file).Fixes #231