-
Notifications
You must be signed in to change notification settings - Fork 475
fix: Merging Dev v4 changes to main #783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Priyanka-Microsoft
wants to merge
37
commits into
main
Choose a base branch
from
dev-v4
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+27
−3
Conversation
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
- Implemented unit tests for the OrchestrationManager class to ensure proper functionality. - Mocked external dependencies including Azure services and agent framework components. - Covered various scenarios including orchestration initialization, agent creation, and event processing. - Added tests for error handling in orchestration execution and WebSocket communication. - Ensured proper participant mapping and workflow execution in orchestration methods.
…st coverage command
…refine pytest command
…les mocking with MagicMock and removing platform-specific skip markers.
…and clarity. Update test cases to ensure proper environment setup and enhance coverage for user language endpoint functionality.
…mocking compatibility issues
…ve platform-specific skip markers and enhance mock setup for cross-platform compatibility.
…patibility issues
…erage for user language endpoint functionality
…pp.py test execution
…letion message is displayed
…suppress unnecessary output
…agent handling and assertions
test: Macae v4 unittestcases kd
fix: reverted unittest case changes
chore: Down merging to dev
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.
Purpose
This pull request primarily introduces a
.coveragercconfiguration file to manage code coverage reporting, and makes minor adjustments to package initialization files. The main focus is on improving test coverage management and cleaning up unnecessary docstrings.Test coverage configuration:
.coveragercfile to configure code coverage measurement, specifying which files and directories to include or omit, and setting up reporting rules.Package initialization cleanup:
__init__.pyfiles tosrc/andsrc/backend/to mark them as Python packages. [1] [2]src/tests/mcp_server/__init__.pyto clean up the test package initialization.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information