Kafka Consumer Error - Note: This element neither has attached source nor attached Javadoc and hence no Javadoc could be found.

I added Kafka related custom Keywords under Keywords package and wanted to consume messages from Kafka Producer. I am getting the error ‘Note: This element neither has attached source nor attached Javadoc and hence no Javadoc could be found’ for 9kafkaCOnsumer.poll method.

1 Like

Hi there, and thanks for posting in the Katalon community! :hugs:

To help you faster, please review our guide on Custom Keyword here: Introduction to custom keywords in Katalon Studio | Katalon Docs. Double-checking the steps and configurations might resolve the issue.

If the doc doesn’t help, feel free to provide more details, and a community member will assist you soon. Thanks for being a part of our community!

Best,
Albert Le

Perhaps you are not familiar with Javadoc, but it is the information about the method (what the method does). In my method below, the Javadoc are the 5 lines with asterisks (i.e. * ).

	/**
	 * Utility to create an instance of TestObject with XPath
	 * @param xpath
	 * @return TestObject
	 */
	public static TestObject makeTO(String xpath) {
		TestObject to = new TestObject(xpath)
		to.addProperty("xpath", ConditionType.EQUALS, xpath)

		return to
	}

It seems your supplier’s methods do not contain information about the methods themselves, or are not formatted “properly”, so that IntelliSense can read them and display the information. If you want to try, copy the above method maybe into the top of a test case, and then save your TC, and add a statement below the method like:

myItem = makeTO('//...')

Now hover your mouse over the “makeTO”, and you should see the Javadoc I have at the top of the method. That’s it. That is all they are.

Note: you would need to supply a XPath pathway for the method to work, but you needn’t supply it if you just wanted to test the Javadoc.

I think that Katalon Studio does not support associating external binary jars downloaded in the Drivers folder with its sources.jar and javadoc.jar. You can not resolve this issue.