when using MCP to update existing test cases, how is the scope of changes typically controlled?
for example, can MCP be limited to updating only descriptions or metadata without modifying test steps, and is there a way to restrict which test cases it can modify in larger projects to avoid accidental changes to shared logic or custom keywords?
Yes, KS MCP does interact with other MCPs through StudioAssist’s Agent Mode, it can create a collaborative ecosystem where multiple MCP servers work together to accomplish complex testing tasks.
In term of use case, I will work with our internal team to provide some for our community, in the mean time, if anyone has any cool use cases, please feel free to share
Currently, the updateTestCase tool can update metadata and also the script. If you want to update only a specific part, pls instruct StudioAssist to do so. Also, by default, StudioAssist will ask you permission before running the tool; you can review what it will do in the input section before approving the change. In the upcoming release, we will have the ability to undo changes, too.