Add explain diagnostic tests#631
Open
PatersonProjects wants to merge 2 commits into
Open
Conversation
…and duplicates, edited docStrings Signed-off-by: PatersonProjects <keldonhoff@gmail.com>
documentdb-triage-tool
Bot
added
the
compatibility test
|
🤖 Auto-triaged by documentdb-triage-tool. Applied: Reasoningcomponent from path globs (test-coverage); effort from diff stats (1061+0 LOC, 8 files); LLM: Adds new test coverage for the explain diagnostic command using CommandTestCase, touching the compatibility tests component within a single area. If a label is wrong, remove it manually and ping |
…case return Signed-off-by: PatersonProjects <keldonhoff@gmail.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.
This PR adds the tests for the explain diagnostic command. Explain is an interesting case, as it has both more internal complexity and crosses more features than many of the other diagnostic commands. It also requires a collection as part of its own function call. Because of this, explain tests primarily rely on CommandTestCase rather than DiagnosticTestCase in order to take advantage of runtime collection resolution.
Ref: Issue #43, #438