Pretty cool ! @kazurayam, I agree: it lacks of unit tests. But the readme page is explicitely asking for demonstrating test-case, validating the new keyword commited. If it’s not enough for debugging, it still is a good guardrail.
Thank you for the feedback. I will follow up with you in the other topic.
Regarding open source Katalon Studio’s current JUnit test cases, there are references to classes in closed source components so we cannot publish them now. But we surely will keep this request in our to-do list.
We need some mechanism which help us resolve the external dependencies automatically and 100% precisely. I quite often dream of a scene where a Katalon Studio project is drastically restructured to be a Gradle project in Eclipse. Gradle provides the state of the art of external dependencies resolution.
Do you mean, for example, com.kms.katalon.core.configuration.RunConfiguration as a closed source component?
Ok, you do not need to distribute them in a source format. You can compile them into binary format and archive into a jar file. Then the keyword project will depend on the katalon-closed-source.jar; that’s all.
Here I assume you have at least 2 distinct source trees — a project for kms-closed-source, and a project for kms-open-source.