Repository navigation
.Net: Add MEVD TestSuiteImplementationTests - #12574
Merged
Merged
Conversation
Shay Rojansky (roji)
requested review from
Dmytro Struk (dmytrostruk) and
westey (westey-m)
June 24, 2025 12:40
Mark Wallace (markwallace-microsoft)
added
the
.NET
Shay Rojansky (roji)
had a problem deploying
to
integration
June 24, 2025 12:40 — with 
GitHub Actions
Error
GitHub Actions
Error
github-actions
Bot
changed the title
westey (westey-m)
approved these changes
Jun 24, 2025
Shay Rojansky (roji)
force-pushed
the
ImplementedTestSuites
branch
from
June 24, 2025 12:47
18cac99 to
19d0043
Compare
Shay Rojansky (roji)
had a problem deploying
to
integration
June 24, 2025 12:48 — with
GitHub Actions
Error
GitHub Actions
Error
Shay Rojansky (roji)
force-pushed
the
ImplementedTestSuites
branch
from
June 24, 2025 12:54
19d0043 to
d5c33d7
Compare
Shay Rojansky (roji)
enabled auto-merge
June 24, 2025 12:54
Shay Rojansky (roji)
temporarily deployed
to
integration
June 24, 2025 12:55 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Mark Wallace (markwallace-microsoft)
approved these changes
Jul 24, 2025
jcruzmot-te
pushed a commit
to thousandeyes/aia-semantic-kernel
that referenced
this pull request
Sep 15, 2025
I noticed that actual test suite implementation is a bit spotty across providers; so this adds a test suite which tests that all other test suites are implemented. We have this in the EF tests as well, also as a way of letting provider maintainers know when a new test suite is introduced which they probably want to implement. Of course, providers can explicitly ignore specific test suites which don't make sense for them. Part of microsoft#10194
This branch was previously 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.
I noticed that actual test suite implementation is a bit spotty across providers; so this adds a test suite which tests that all other test suites are implemented. We have this in the EF tests as well, also as a way of letting provider maintainers know when a new test suite is introduced which they probably want to implement. Of course, providers can explicitly ignore specific test suites which don't make sense for them.
Part of #10194