[MCP Use Case 6] Identify duplicated test cases

The video demonstrates an easy way to clean up a test project that has become messy with a lot of duplicate test cases over time. The process involves asking Studios to find all the duplicate test cases in the project. Ajith showed how this is done by pasting a prompt to “identify duplicate test cases,” selecting “agent mode,” and running it. It then shows a summary of duplicated test cases, pointing out two test cases that are similar and suggesting an action.

Hope you find this short demo useful,

The Katalon Community Team

1 Like

Useful insights

one thing i’d add when using the MCP Agent is to review the merge suggestions bit by bit, just to make sure nothing important gets removed

after that letting the Agent double check or rerun related tests feels like a safe way to confirm everything still behaves as expected especially in older projects with lots of duplicates

1 Like

Thank you for your great insight Depa ^^

1 Like

Also better to start with small sets/folders before processing entire repositories. Review the changes and then scale up accordingly

1 Like