# Which is the better approach? Calling test cases multiple times or calling custom keywords intead? **URL:** \ **Category:** Web Testing\ **Tags:** katalon-studio\ **Created:** [September 15, 2022, 7:04am UTC](https://forum.katalon.com/t/which-is-the-better-approach-calling-test-cases-multiple-times-or-calling-custom-keywords-intead/78564 "2022-09-15T07:04:53Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\ **Post date:** [September 15, 2022, 7:51am UTC](https://forum.katalon.com/t/which-is-the-better-approach-calling-test-cases-multiple-times-or-calling-custom-keywords-intead/78564/3 "2022-09-15T07:51:12Z")
Another aspect. It is easier to develop & test Test Case scripts in Katalon Studio. You can run a Test Case by single button click, Katalon Studio emits verbose execution log, you can interactively see how your Test Case ran. On the other hand, it is difficult to develop quaility Groovy classes as custom Keywords in Katalon Studio. Katalon Studio does not offer any built-in support of unit-testing of custom Keywords. > I once developed [junit4ks](http://forum.katalon.com/t/running-junit4-in-katalon-studio/12270) to perform unit-test over my custom classes. Often I develop custom classes to use in a Katalon project OUTSIDE Katalon Studio. I use IntelliJ + Gradle where I carry out enough unit-testing using JUnit4. Once developed, I will create a jar, import the jar into the Katalon project, use the classes in the jar from Test Cases. A practical suggestion from me for easier path could be: 1. use a composite of multiple Test Cases, rather than Keyword classes 2. try to minimize the verbosity of step-execution logs emitted by Katalon Studio. See the above-mentioned post how to. --- _[View the full topic](https://forum.katalon.com/t/which-is-the-better-approach-calling-test-cases-multiple-times-or-calling-custom-keywords-intead/78564)._