I'm not sure if I understand your question or intend correctly. If you are the one developing the plugin, can you test it locally to make sure that it works before uploading to the production server? You can write Java test cases to make sure that the plugin is doing the exact thing it supposed to do.

Check the server log too as that would be the most likely places to catch any error thrown out by the plugin.

is there any automated testing or compatibility check feature available in Joget so that we will upfront know what is the impact of new plugin in the all the applications?

is there any automated testing or compatibility check feature available in Joget so that we will upfront know what is the impact of new plugin in the all the applications?

Plugins are normally of OSGI type. Once we upload the plugin, if there's library/dependencies conflict, it will appear immediately upon uploading and it will fail.

If your plugin is solving specific problem, then you will need to write the specific test for it.

If it is an existing plugin that we are updating, normally, I will check for its existing usages by searching for the java class path name in the database.

For example, if it is a process tool plugin, they will be used inside:-

1. process flow's tool mapping (table: app_package_activity_plugin column: pluginProperties)
2. plugin default properties (table: app_plugin_default, column: pluginProperties)
3. form post process (table: app_form, column: son)

So, it is pretty much dependant on what kind of plugin you are developing hence the way to find its usages/table name would differ.

Thank You...