examples excluded#4
Closed
elenagaljak-db wants to merge 2 commits into
Closed
Conversation
zlata-stefanovic-db
added a commit
that referenced
this pull request
Jun 24, 2026
## Summary The C++ SDK test suite (`tests/`) — the tiny hermetic in-repo harness plus unit tests for config conversion, errors, the headers trampoline, proto schema, and the SDK — and the `add_subdirectory(tests)` wiring. Part of the #415 split (5/6). ### Merge order **Stacked on #4 (core).** Merge after core; this branch is based on it. Draft until the stack is reviewed. Split from #415. Signed-off-by: Zlata Stefanovic <zlata.stefanovic@databricks.com>
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 changes are proposed in this pull request?
Provide the readers and reviewers with the information they need to understand
this PR in a comprehensive manner.
Specifically, try to answer the two following questions:
major changes to allow the reader to quickly understand the PR without having
to look at the code.
reader might be missing. For example, were there any decisions behind the
change that are not reflected in the code itself?
The “why part” is the most important of the two as it usually cannot be
inferred from the code itself. A well-written PR description will help future
developers (including your future self) to know how to interact and update your
code.
How is this tested?
Describe any tests you have done; especially if test tests are not part of
the unit tests (e.g. local tests).
ALWAYS ANSWER THIS QUESTION: Answer with "N/A" if tests are not applicable
to your PR (e.g. if the PR only modifies comments). Do not be afraid of
answering "Not tested" if the PR has not been tested. Being clear about what
has been done and not done provides important context to the reviewers.