Repository navigation
Conversation
…ries Add baselibs feature integration tests that verify the Eclipse S-CORE base libraries end-to-end on the deployed target image and reference the feat_req__baselibs__* feature requirements they cover, so the coverage shows up in the platform verification report. - Add an on-target demo binary (feature_integration_tests/ baselibs_integration_tests/demo) exposing one subcommand per baselibs feature library (json, utils/base64, bitmanipulation, hash/crc32, containers, result), each printing a deterministic line. - Add a py_itf_test suite (:bit) that drives the demo on the target and asserts the output, annotated via @add_test_properties with the feat_req__baselibs__* needs. The attribute_plugin records PartiallyVerifies into the JUnit XML, which docs-as-code turns into testlink attributes. - Bundle the demo binary into //images/linux_x86_64:image. - Run the suite in the test_and_docs job before the documentation build so the source code linker picks up the test results from bazel-testlogs, mirroring the platform integration tests wiring.
|
The created documentation from the pull request is available at: docu-html |
Delete before merge. Proves the baselibs feature integration tests feed the platform verification report, which the pull_request_target pipeline cannot show pre-merge.
Add on-target subcommands and ITF tests for the concurrency, filesystem, memory, static reflection and flatbuffers libraries, and extend the containers and result tests to also partially verify abi_containers and panic_free_development. Together with the existing tests this now covers all 14 feat_req__baselibs__* feature requirements.
antonkri
force-pushed
the
feat/baselibs-integration-tests
branch
from
October 2, 2026 10:35
fecac14 to
9478d36
Compare
Remove the push-triggered baselibs coverage preview (its job was done) and shorten the inline descriptions of the Docker Buildx and baselibs test steps.
This branch has not been 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
1 participant
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
Adds baselibs feature integration tests that verify the Eclipse S-CORE base libraries end-to-end on the deployed target image and reference the
feat_req__baselibs__*feature requirements they cover, so the coverage surfaces in the platform verification report.How
Follows the same pattern as the platform integration tests (#377):
feature_integration_tests/baselibs_integration_tests/demo) with one subcommand per baselibs feature library, each printing a deterministic line:json→feat_req__baselibs__json_librarybase64→feat_req__baselibs__utils_librarybitmanip→feat_req__baselibs__bitmanipulationcrc32→feat_req__baselibs__hash_librarycontainers→feat_req__baselibs__containers_libraryresult→feat_req__baselibs__result_librarypy_itf_testsuite:bitthat drives the demo on the target and asserts the output. Each test is annotated via@add_test_properties(partially_verifies=[...]); theattribute_pluginrecordsPartiallyVerifiesinto the JUnit XML, which docs-as-code's source code linker turns intotestlinkattributes on the referenced requirement needs.//images/linux_x86_64:image.test_and_docsstep runs the suite before the documentation build so the source code linker picks up the results frombazel-testlogs(manual-tagged ITF tests are otherwise skipped bybazel test //...). A Docker Buildx setup step is added for the image deployment.Coverage mechanism
The verification report's testlinks come from runtime JUnit XML ingestion. Running
:bitin the same job, before the docs build, is what makes thefeat_req__baselibs__*coverage appear in the baselibs feature section of the platform verification report.Notes / open points
bazel test //feature_integration_tests/baselibs_integration_tests:bitrequires the Linux OCI image build, which is currently blocked locally by a pre-existing, unrelatedconfig_managementBUILD issue (not introduced here). The demo binary, image tar, BUILD parsing, plugin wiring and formatting were all validated locally.Set up Docker Buildxstep may need to be de-duplicated with the one that PR adds.Draft for review.