feat: add automation_status field to test case creation #116
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
- Add automation_status as optional field to TestCaseCreateRequest interface - Add Zod schema validation with documentation for common values - Update sanitizeArgs function to handle automation_status null values - Add test coverage for the new field - Maintains backward compatibility (optional field)
Collaborator
ruturaj-browserstack
approved these changes
Aug 12, 2025
Vishalan
approved these changes
Aug 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
🔧 Add automation_status field to test case creation
📋 Summary
This PR adds support for the
automation_statusfield when creating test cases via the BrowserStack Test Management API. This field allows users to specify the automation status of test cases (e.g.,not_automated,automated,automation_not_required) directly during creation.🎯 Motivation
The
automation_statusfield is already supported by the BrowserStack Test Management API and is returned in API responses, but was not exposed in the MCP server's test case creation functionality. This created a gap where users couldn't set this important QA workflow field during test case creation.🔍 What Changed
automation_status?: stringtoTestCaseCreateRequestinterfaceautomation_statusfield to the Zod schema with validation and documentationsanitizeArgs()function to handle null values for the new field✅ Backward Compatibility
🧪 Testing
automation_statusfield📚 API Reference
This aligns with the official BrowserStack API documentation:
not_automated,automated,automation_not_required🎉 Impact
Users can now fully manage test case automation status through the MCP server, enabling complete QA workflow automation without manual steps in the BrowserStack UI.
Files Changed: 2 files, 9 insertions
src/tools/testmanagement-utils/create-testcase.ts- Core implementationtests/tools/testmanagement.test.ts- Test coverage