-
Notifications
You must be signed in to change notification settings - Fork 0
Implement Generic Profile Test Framework #32
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
Implement Generic Profile Test Framework #32
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…implementation
|
@jules review and evaluate latest changes. |
I have reviewed and evaluated the latest changes. Summary:
The codebase is now cleaner and uses the unified testing strategy. |
d9e53a0 to
41c4764
Compare
…-implementation
…d structure; added new test cases for retrieving and managing articles, issues, and commands.
…data parameters, adjusted test scenarios, and improved duration handling
…-from-implementation-plan
…coverage requirements
- Changed all instances of 'developer-profile.json' to 'developer-profile-oauth.json' in test files to ensure OAuth profile is used for testing. - Added mock API server responses for user and personal access tokens in the HTTP integration tests. - Enhanced the MCP process to include Authorization header when apiToken is provided. - Updated environment variables for OAuth in various E2E tests to ensure proper authentication flow.
…regex request assertions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…st-template-transition
9927b95 to
adb313c
Compare
02b9887 to
1b5237a
Compare
Introduced a new generic testing framework for MCP profiles. This allows defining integration tests declaratively in
profile.test.jsonfiles alongside the profile definition. Key components include:src/testing/test-schema.ts: Defines the schema for test definitions.src/testing/test-loader.ts: Loads and validates test files.src/testing/dynamic-mock-server.ts: Uses MSW to dynamically mock OpenAPI operations based on test scenarios.src/testing/generic-profile.test.ts: A Vitest suite that discovers and runs all profile tests.src/testing/template-utils.ts: Supports dynamic values like{{$randomInt}}and{{$uuid}}in test data.Also verified the framework by adding
profiles/gitlab/developer-profile.test.jsoncovering success, error, timeout, and dynamic data scenarios.PR created automatically by Jules for task 14063437140109787182 started by @davidruzicka